I am an administrator for a managed hosting provider. We’ve found several servers within our datacenters using Percona Server which did not properly start MySQL after an update was applied using yum. The logs paint a pretty clear picture that indicates that the server was stopped during the update, but never started back up. I am curious to see if others have experienced similar issues, and I’d like to know if this will be fixed in future updates if it’s determined to be an issue with the rpm.
So far as I’ve found so far, the issue appears to only affect RHEL 6 servers running Percona-Server-server-55-5.5.30-rel30.2.500. We only run RHEL6 on x86_64 bit arch so I can’t say whether or not i386 would be affected. Below are the relevant log lines from yum.log and mysqld.log which help to associate the shutdown to the update.