Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I originally installed mySQL on OSX and it started fine. I was able to connect with mySQL workbench and create a database. However, after a reboot mySQL will no longer start.

The launch fails with the following message taken from the error log:

[ERROR] /usr/local/mysql/bin/mysqld: unknown option '--skip-locking'

Also checked the activity monitor and there is no other mySQL process running.

share|improve this question

It looks like an upgrade has incremented your versions, because on my systems running 5.0.x the mysqld supports --skip-locking, but by 5.5 it is gone....

# /usr/libexec/mysqld --verbose --help | grep skip-lock
  --skip-locking      Deprecated option, use --skip-external-locking instead.

[root@g0801 ~]# rpm -q mysql-server

Now it is gone, from the 5.5 binary options....

$ rpm -q mysql-server

 $ /usr/libexec/mysqld --verbose --help 
 No such option --skip-locking
share|improve this answer
I installed mySQL 5.5.23 on OSX and there was no other version of mySQL out there at the time. Now I did add mySQL as a server within Eclipse and selected the option to "Use Tomcat Installation". It appears to start correctly within Eclipse so I'm wondering if it changed one of the config files? – Jeff Cope May 1 '12 at 11:00
sounds plausible, if there is nothing in the services script, then to check whether any of the service control options got carried over. I am not familiar with Max OS x, but it seems have a "services control menu" which might have those legacy options enabled. – Tom H May 1 '12 at 13:57
I was unsuccessful in getting this to run. Any suggestions for what I might check? I did try re-installing (without running an uninstall) and that did not resolve the issue. – Jeff Cope May 2 '12 at 12:32
up vote 0 down vote accepted

Deleting the ../etc/my.cnf file allowed the server to start successfully.

share|improve this answer
Please be sure to mark this answers as "accepted" when you are able. – jscott May 3 '12 at 13:07

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.