R
redrob
Guest
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
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