Our resolution was to simply kill all of the running processes. There seems to be a problem with how current versions of OS X store the mysql socket and how php My Admin looks for it.
Then, OS X's launchd did it's work and restarted My SQLd, which was definitively running as installed by Homebrew.
The easiest way is to remove your configuration file, and try to start the My SQL server again: Backup your My SQL configuration first.
We're looking for long answers that provide some explanation and context.
Don't just give a one-line answer; explain why your answer is right, ideally with citations.
Sometimes the program might be having issues of its own and require to be diagnosed by your operating system itself.
In that case, it won’t start normally and hence, you might have to run it in safe mode.
Try running My SQL on safe mode by: I wrote explaining most of them!