I'm running a Mid-2012 Macbook Air with OS X 10.8.2 and mysql was installed with homebrew. Please take note that you need to run mysql_install_db from the with top level of the mysql directory (IE, usr/local/Cellar/mysql/5.5.25).
Running it directly within the /scripts directory does not give it enough context for it to run.
Unfortunately mysql was also upgraded to 5.6.10 from 5.5.14. I decided to go back to my old setup and did a It seems that My SQL process is running hence you are unable to use the port.
So I manually ran and then attempted to start it again. But worse, no file in the var dir - it was in the "data" dir!
so scripts/mysql_install_db sets up camp in /usr/local/mysql/var, but the rest of the application seems to want to do its work in /usr/local/mysql/data!
So I just edited /etc/and under the section [mysqld] I added a directive to explicitly point mysql's data directory to var (as I normally expect it to be any how), and after doing so, mysqld starts up just fine.
The directive to add looks like this: datadir = /usr/local/mysql/var Worked for me. I had this problem while trying to brew upgrade on Mac OS X 10.7.5.
In the end, cleaning up and following brew doctors advice made it possible to run through the setup described above. I copied the entire lampp folder from /opt to a new server.
So a note to anyone else passing by; don't try to cheat the brew doctor and think you know better! When I tried to start up mysql I got a message: The server quit without updating PID file.
[mysqld] port = 3306 socket = /tmp/skip-external-locking key_buffer_size = 16K pid-file=/var/run/mysqld/[mysqld_safe] log-error=/var/log/pid-file=/var/run/mysqld/I tried following these instructions a million times but never got it to work.
I tried to "cheat" by not cleaning up all the things brew doctor warned me about since I thought they didn't make a difference.
resulted in the error: "The server quit without updating PID file" I noticed something odd in the installation instructions though.
It has ownership changed to mysql for the directory "data", but not to "var"; this is unusual because for years I have had to ensure that var directory was mysql writable.