Parallels' MySQL 5.5 wipes /etc/my.cnf

[HostaHost]

Version: 11.5.30 CentOS 6 115140407.17 x86_64

Description: On June 30th 4am EST we had a client's server become non-operational when Plesk did it's daily auto update install. The server is running Parallels' release of MySQL 5.5 instead of the CentOS 6 x64 native MySQL 5.1. An update to the Parallels MySQL was installed and it replaced the /etc/my.cnf with a stock copy instead of preserving what had been there, so all the custom configuration was lost. This issue caused data loss.

Steps to reproduce: Install Plesk 11.5 on Centos 6 x64, update to a non-current version of Parallels' MySQL 5.5, let auto updates upgrade to the lates

ACTUAL RESULT: /etc/my.cnf is replaced with a stock copy

EXPECTED RESULT: /etc/my.cnf will be preserved

 

[IgorG]

update to a non-current version of Parallels' MySQL 5.5, let auto updates upgrade to the lates

How should I do this exactly?

 

[HostaHost]

I would assume you have access to prior versions of your company's releases? Install an older centos 6 x86_64 mysql 5.5 rpm, then let auto updates apply the latest version.