During a recent update using custom build, one of the items was mysql going from 5.1.55 to 5.1.56, not a big update I assumed etc..
Well after mysql was updated it failed to start throwing the following error.
Rename the file back to its original name and try starting the server.
Once you get the “Manager of pid-file quit without updating file” error message, head to the mysql error log.
Manager of pid-file quit without updating file First verify that this is true. If you do not know where is, you can do “locate my.cnf”.
If mysql server starts fine when you rename my.cnf, it confirms that it is having a problem with your file.
Inno DB: If that is the case, please refer to Inno DB: [ERROR] Plugin ‘Inno DB’ init function returned error.
If it is not fresh installation, do a rpm -Uvh instead) Remove all contents of /var/lib/mysql/ directory Re-install RPM check if /var/lib/mysql/mysql/is created after installing RPM Then give a service mysql start and watch logs.This error log may be under your system’s log directory (/var/log/mysql) or under the mysql data folder (usually /usr/local/mysql/data). In my case the error log listed the following items: Inno DB: No valid checkpoint found.Inno DB: If this error appears when you are creating an Inno DB database, Inno DB: the problem may be that during an earlier attempt you managed Inno DB: to create the Inno DB data files, but log file creation failed.Inno DB: File name ./ibdata1 Inno DB: File operation call: 'open'.
If SElinux is the problem, then you should monitor and make it work (check: My SQL 5.6 and SELinux are arguing) You can also disable it permanently at /etc/sysconfig/selinux changing enforcing to either permissive or disabled.I'm not sure why this line above didn't cause any issues with 5.1.55 and threw 5.1.56 into a frizzy...