In this article, we have listed the most common fixes which work on most cases.
I deleted ib_logfile0 and ib_logfile1 and I was able to start mysql server without any problems.
These files are usually under the mysql data directory.
The mysql.socket is no longer visible in /tmp eventhough mysql thinks it is.
Getting these bad boy errors on your mysql on OSX, there seems to be lots of solutions about how to fix this, Google hell, this more than likely happens if mysql is running and the OS is updated like from OSX Mountain Lion to Mavericks.
Therefore, I need to start it again after the update is done. During the system upgrade, the OS may disable some of your daemons.
Unfortunately, the upgrade process is not smooth every time. Instead of troubleshooting each one by one, the easiest way is to start everything over.
But these may not solve the issue, I found a clean install of the latest mysql will address the issue by installing all components from the dmg.
Download the latest mysql and pick the Mac OS X 10.7 (x86, 64-bit), DMG Archive version.
If mysql server starts fine when you rename my.cnf, it confirms that it is having a problem with your file.