Qmail problems after upgrading to 8.3

[redrob]

I did something really stupid over the weekend, I upgraded to 8.3. No reason, I did not need any of the new features... I just clicked upgrade to be current.

Bad idea!

The upgrade reported it went fine, no problem.

Turns out QMAIL has an issue. It starts, stops and runs fine. However when someone connects via SMTP (port 25) it spits out an error like this:

/var/qmail/bin/relaylock: /usr/lib/mysql/libmysqlclient.so.14: no version information available (required by /var/qmail/bin/relaylock)

Any server trying to send a message sees the error, and disconnects. So while qmail thinks it is running, no messages can be delivered.

I spent hours trying to resolve the problem with no luck. I broke down and purchased
a support ticket with SWSoft. Their 1st level support could not find the problem
and sent it up to second level.

Second level claims that mysql is causing the problems (version 5.0.22), and suggest
I roll it back to 4.1 - I waited two days, and paid for that answer?!?!

For the life of me I don't even recall updating it to version 5, I think it just happened
automatically when using YUM update.

I would rather not roll back to 4.1, as who knows what else it would break.

Other than that error message, there are no other errors being reported, that is all I have
to go on. Can anyone shed some light on the situation?


Thanks,

Red Rob

 

[redrob]

I just found the problem is affecting other parts of the system. When trying to do a backup, I got the following:

/usr/local/psa/admin/sbin/mailmng: /usr/lib/mysql/libmysqlclient.so.14: no version information available (required by /usr/local/psa/admin/sbin/mailmng)
/usr/local/psa/admin/sbin/backup_sign: /usr/lib/mysql/libmysqlclient.so.14: no version information available (required by /usr/local/psa/admin/sbin/backup_sign)

So it does seem to be that updating to 8.3 has had some type of effect with MYSQL.... any ideas?

 

[dirty@]

you didn't specify your operating system... anyway, the most probably it means that you used some third yum repository and your mysql4 was updated to mysql5 during plesk update.. os vendors do not put such major updates as mysql4->mysql5 in their default os update repositories..

what you may do now - find in this repository and install package with mysql client libraries of previous version, the most probably it will be named like 'libmysqlclient14'

 

[redrob]

Oh yea, operating system. It is CentOS, and the box has been running for 1+ years without any issues and I don't recall updating to a different YUM repository. I will check the YUM config files and see what I find.

Thanks for the input.

 

[redrob]

what you may do now - find in this repository and install package with mysql client libraries of previous version, the most probably it will be named like 'libmysqlclient14'

Well Dirty,

Tell me where to send the money!

I spent $75.00 on purchasing the Plesk support, and after more than two days they could not
give me an answer.

Your comments, based on my half complete description led me to the clues necessary.

I found the following in the yum cache folder from the centosplus repository, so it
appears that I did infact update back in 2006... and only now it is coming back
to bite me in the ***.


-rw-r--r-- 1 root root 13748987 Oct 7 2006 kernel-2.6.9-42.0.3.plus.c4.i686.rpm
-rw-r--r-- 1 root root 3962670 Oct 7 2006 kernel-devel-2.6.9-42.0.3.plus.c4.i686.rpm
-rw-r--r-- 1 root root 3986314 Oct 7 2006 kernel-hugemem-devel-2.6.9-42.0.3.plus.c4.i686.rpm
-rw-r--r-- 1 root root 3976504 Oct 7 2006 kernel-smp-devel-2.6.9-42.0.3.plus.c4.i686.rpm
-rw-r--r-- 1 root root 3138900 Jul 21 2006 mysql-5.0.22-1.centos.1.i386.rpm
-rw-r--r-- 1 root root 1192913 Jul 21 2006 mysqlclient14-4.1.14-4.2.c4.1.i386.rpm
-rw-r--r-- 1 root root 10206208 Jul 21 2006 mysql-server-5.0.22-1.centos.1.i386.rpm
-rw-r--r-- 1 root root 3432718 Nov 20 2006 php-5.1.6-1.2.1.centos.i386.rpm
-rw-r--r-- 1 root root 103467 Nov 20 2006 php-gd-5.1.6-1.2.1.centos.i386.rpm
-rw-r--r-- 1 root root 48486 Nov 20 2006 php-imap-5.1.6-1.2.1.centos.i386.rpm
-rw-r--r-- 1 root root 991427 Nov 20 2006 php-mbstring-5.1.6-1.2.1.centos.i386.rpm
-rw-r--r-- 1 root root 77098 Nov 20 2006 php-mysql-5.1.6-1.2.1.centos.i386.rpm
-rw-r--r-- 1 root root 61713 Nov 20 2006 php-pdo-5.1.6-1.2.1.centos.i386.rpm
-rw-r--r-- 1 root root 350228 Jan 2 2007 php-pear-1.4.9-1.2.centos.noarch.rpm
-rw-r--r-- 1 root root 85365 Nov 20 2006 php-xml-5.1.6-1.2.1.centos.i386.rpm


I entered the following command: yum update mysqlclient14

The update was done in 20 seconds, and the system is back up and running!


Thank you very much for your input!


Red Rob

 

[dirty@]

never mind

send this as bug report to swsoft, imho plesk rpms should have dependency to this mysql library if they use it and do not allow silent mysql update if this dependency is not satisfied...