Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

getting a Start MySQL Failed error in the GUI.. when i attempt to start mysqld from the CLI i get the following error:

→ /Applications/MAMP/Library/bin/mysqld         
120623 23:12:47 [Warning] Setting lower_case_table_names=2 because file system for /Applications/MAMP/db/mysql/ is case insensitive
120623 23:12:47 [Note] Plugin 'FEDERATED' is disabled.
120623 23:12:47 InnoDB: The InnoDB memory heap is disabled
120623 23:12:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120623 23:12:47 InnoDB: Compressed tables use zlib 1.2.3
120623 23:12:47 InnoDB: Initializing buffer pool, size = 128.0M
120623 23:12:47 InnoDB: Completed initialization of buffer pool
120623 23:12:47 InnoDB: highest supported file format is Barracuda.
120623 23:12:47  InnoDB: Waiting for the background threads to start
120623 23:12:48 InnoDB: 1.1.5 started; log sequence number 1595675
120623 23:12:48 [ERROR] /Applications/MAMP/Library/bin/mysqld: unknown option '--skip-locking'
120623 23:12:48 [ERROR] Aborting

120623 23:12:48  InnoDB: Starting shutdown...
120623 23:12:49  InnoDB: Shutdown completed; log sequence number 1595675
120623 23:12:49 [Note] /Applications/MAMP/Library/bin/mysqld: Shutdown complete

i have deleted the mysql.pid file located at /application/mamp/tmp/mysql/mysql.pid and i still get the error above. I can't find where MAMP has set --skip-locking set, my.cnf doesnt have it anywhere.

Activity monitor gives me a mysqld process running by me, and everytime i KILL the process both via Activity Monitor and via kill =9 pid it starts right back up.. Sampling the process points back to the MAMP mysqld.. wtf?!

About to throw MAMP out the window and boot up a VM of CentOS =)

share|improve this question
About to throw MAMP out the window and boot up a VM of CentOS =) Actually, that's the best idea IMHO. –  SvW Jun 24 '12 at 6:33
Yeah its just a development environment, and honestly this app is a piece of crap =). However my problem was user error. the production environment is a CentOS DV4 server @ mediatemple. –  gorelative Jun 24 '12 at 6:36
add comment

1 Answer

i installed another application for my own AMP stack to replace MAMP called WebStart, which wrote a my.cnf file to /etc/my.cnf as a result MAMP is also configured to look there by default, and then the /applications/mamp/tmp/mysql/my.cnf file. Due to this scenario the my.cnf file located at /etc/my.cnf had the line --skip-locking in it.

I deleted the /etc/my.cnf file and then started MAMP up, and started mysql. All is working now.

For anyone else at their wits end, make sure you only have one instance of MySQL installed, this includes mysql.pid and my.cnf files. Search your entire mac for them.

share|improve this answer
add comment

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.