MySQL Service Startup Issues

Have you made sure the mysql user has proper access to that directory? Show us the output of:

ls -al "/Volumes/Macintosh HD2/ServiceData/MySQL/"

Also, I think someone had similar trouble in another thread and it was due to the space in the hard drive name, but I'd verify the permissions first.

Hi, as far i as i know MYSQL doesn't like its data being stored on a partition with spaces in the name aka Macintosh HD2.

best fix is so make sure all your services data is on a partition with no spaces "Servicesdata"
i also made this error, easiest fix was reinstalling for me.

hope this helps.

Hi,

I recently had a bit of a fight myself trying to get MySQL up and running on a new Mac mini with Snow Leopard Server using the second disk. After trawling through log files and scripts, the way I got round it was to install the service by ticking the checkbox in Services but DON'T start the MySQL service at this point, instead drop into a Terminal command prompt and do ...

cd /Volumes/Macintosh\ HD2/ServiceData/MySQL
sudo /usr/bin/mysql installdb --user=_mysql --datadir=.

This installs the default database into the '.' directory (i.e. the current one set by the previous 'cd' command, which is the relevant place on the second disk).

So long as that runs without error, THEN start the MySQL server and check the log file, everything should be running ok.

Incidentally, as I'd already tried to install it using Server Admin I found myself in a situation were the MySQL process was constantly trying to start and failing and I couldn't stop it without a reboot so to stop that and clean up a bit before running the above install script, again in a Terminal command prompt I did 'sudo serveradmin stop mysql' and then removed all the files using Finder in the 'Macintosh HD2/ServiceData/MySQL' folder. Don't delete the 'MySQL' folder it's self just the files in there.

Mark

I got myself into a jam with the same setup--new Mac Mini with Snow Leopard Server pre-installed. I started MySQL, and changed the root password within a few seconds of each other (not sure in what order) and got MySQL into a permanent "Starting..." state. I couldn't stop the service, even from the command line. Even after rebooting, it would still be "Starting...". The service log showed that it was attempting to start every minute or so and failing. I also couldn't disable the service.

The reason is that the database location, of course, can't have a space in it, but I couldn't get the database location setting to change in the startup script for the service, even though Server Admin showed it as changed. Server Admin will let you edit the database location and save it. However, it will not commit the new setting to the launch script if the service is in the "Starting..." state. It also won't let you disable the service when it is in the "Starting..." state. Essentially, the Server Admin GUI and the serveradmin command line application have the appearance of working, but don't do anything when the service is in the "Starting..." state.

I resolved this by editing the database location in the mysql service's LaunchDemon plist file, unloading the file, recursively deleting all files in the database location, re-saving the database location in Server Admin, and then re-enabling and starting the service.

You can edit the plist file here:
/System/Library/LaunchDaemons/org.mysql.mysqld.plist

You can unload the service with this command:
sudo launchctl unload /System/Library/LaunchDaemons/org.mysql.mysqld.plist

Hi mheydon

Thanks a lot for sharing your solution, which seems to be the solution to my problem as well !

Thanks....