101112 Inno DB: Initializing buffer pool, size = 128.0M 101112 Inno DB: Completed initialization of buffer pool 101112 Inno DB: highest supported file format is Barracuda.
This occurs when My SQL is upgraded to a later version or due to insufficient permission and ownership issue in My SQL data directory.
For conventional installations, without brew, like mine, the solutions above doesn't worked.
The solution came with the permission repair, using the Utilities Disk App from OS X.
At this point, you might think I’m joking but trust me on this and don’t laugh it off when I ask you to – first, breathe, then – restart your system.
You will be thanking me if it works and in case it doesn’t, well then read onwards in this article! This method might be something that looks insignificant but can do wonders sometimes when the trouble is just a little lag in your PC or software.
The server quit without updating PID file (/var/lib/mysql/yourservername.pid)” is thrown when My SQL fails to start.
The PID file in the My SQL data directory is gone and My SQL wont behave without it.
It seems you have issue with you permission on mysql datadir.Unfortunately, the upgrade process is not smooth every time. Instead of troubleshooting each one by one, the easiest way is to start everything over.For example, I experienced this problem today after upgrading the Apache and Ruby (Yes, My SQL is not part of the update), and I got this error message afterward.After rebooting the computer, the error message is gone.If you have modified your My SQL configuration file, My SQL may not like it few versions after (My SQL is not backward compatibility friendly).In that case, it won’t start normally and hence, you might have to run it in safe mode.