Atomicorp

I got MySQL 4.1.14 installed today, but now are in loads of troubles:

The MySQL function PASSWORD generates passwords which look quite different from the old passwords.
This means every client who uses the PASSWORD-function in MySQL will have problems.

Also it means that my mail cannot get sent; I think this is also caused by MySQL.

Any solutions to this?

From webmail (Horde) I get the following:
Warning: fsockopen(): unable to connect to 127.0.0.1:25 in /usr/share/psa-horde/pear/Net/Socket.php on line 108

PS: it might also be in dcc or razoragents, since they updated as well?

Uninstalling dcc/razoragents didn't solve it.

Read this thread and see if it helps:

http://forum.plesk.com/showthread.php?s=&threadid=28053

Have you ran this: (thought that this ran automatically, but I'm not sure) and do you have oldpasswords in /etc/my.cnf?


You could also have a look at the last post here:
http://ez.no/community/forum/install_co ... tall_3_7_0

(tells how to change the passwords to "old-passwords")

Hello Griffith,
Thanks for your response, however, this does not fix my problem. I am now running with the old-password on, and everything works... connecting and such no problem. Only got a problem with sending mail.

I removed the dcc and razoragents rpm's, but it didn't fix my problems.

that fsockopen error generally pops up when you're running out of file descriptors. Are you running a server with a lot of domains? Each domain will use up 2 or 4 FD's, and the default limit is 1024.

@Scott: A lot of sites indeed, we feature over 600 on this one. How can I check this?

Yep that will do it, you need to recompile php, openssl, imap and apache for high file descriptor environments. I thought I had set up php to be built that way automatically, but I might have missed it, what distro are you on?

Fedora Core 2 (2.6.10-1.771_FC2smp)

I might have been completely mistaken about the update... I just recently learnt that my server crashed this morning, and was rebooted at 7:40 ... that was also about the time that emails stopped being delivered, according to the mail log. 2 hours later I performed the update, so it might have been an earlier update.

Just to be complete, in addition to my previous message:
09/27/05 10:57:20 Updated: php-mbstring 4.4.0-3.rhfc2.art.i386
09/27/05 10:57:20 Updated: php-pgsql 4.4.0-3.rhfc2.art.i386
09/27/05 10:57:20 Updated: php 4.4.0-3.rhfc2.art.i386
09/27/05 10:57:20 Updated: php-mysql 4.4.0-3.rhfc2.art.i386
09/27/05 10:57:20 Updated: php-domxml 4.4.0-3.rhfc2.art.i386
09/27/05 10:57:20 Updated: mysql-server 4.1.12-1.rhfc2.art.i386
09/27/05 10:57:20 Updated: mysql 4.1.12-1.rhfc2.art.i386
09/27/05 10:57:20 Updated: php-pear 4.4.0-3.rhfc2.art.i386
09/27/05 10:57:20 Updated: php-ldap 4.4.0-3.rhfc2.art.i386
09/27/05 10:57:20 Updated: mysql-compat 4.1.12-1.rhfc2.art.i386
09/27/05 10:57:20 Updated: php-imap 4.4.0-3.rhfc2.art.i386

These are the updates of the last time.


/sbin/sysctl -a|grep file-max
shows:
fs.file-max = 102653

Scott, I think you might be so right in this.

/sbin/sysctl -a|grep file
shows me:

fs.file-max = 102653
fs.file-nr = 3510 0 102653


The 0 is the number of available file allocates... I think this proves you are correct, right? But how should I increase this ... the 102.653 is the maximum, but it's not even near that (3510 open!)... I don't understand at all.

I still don't understand how this can be a problem, but now I have rebooted the server again and everything seems to go through well...

Its a hard limit set at compile time in the binaries themselves, the default is 1024 so if you had 250 domains, each with SSL, that would use up 1000 File descriptors. The variation for most people comes from a number of those domains being forwarders, subdomains, or otherwise not using SSL.