Am 18.08.2015 um 10:55 schrieb tony at softins.co.uk (Tony Mountifield): > In article <55D2ED32.6040000 at hogranch.com>, > John R Pierce <pierce at hogranch.com> wrote: >> On 8/18/2015 1:27 AM, Tony Mountifield wrote: >>> That may well be the case, but isn't relevant to the point I'm making, >>> which is that something changed in openssl-0.9.8e-36 that has broken something. >> >> mysql 5.0 and openssl 0.9.8 are both ancient and way past their >> expiration date. > > Maybe so, but still a side issue. Openssl 0.9.8e was recently updated. > Some change in this update has broken something. I would like to understand > what, and so ought the package maintainers. C5 isn't EOL until March 2017. important in this case is, that a different combination of software packages, that are not in the scenario of upstreams philosophy, are not supported and can lead to unexpected behavior. As always recommended by any advisory: "Before applying this update, make sure all previously released errata relevant to your system have been applied." Why EL5 is on MySQL 5.5 and EL6 on MySQL 5.1 is a different question (only upstream can answer). I recommended to update your (client and server) systems to the current supported state (5.11) with all relevant updates applied. This includes the mentioned migration to mysql55-mysql. Our EL5 setup/service passes this migration seamless. And then check your problem in this new environment ... -- LF