Fix for running MySQL 5.5.8 under MacOS X 10.6.5 (Snow Leopard)

Oracle recently released the latest MySQL 5.5.x versions. Despite of having tones of fixes and supposedly running much faster and (finally) making InnoDB the default storage engine, it is always good to keep up to date with latest releases.
But, as in the past, MaxOS X users always have to battle with getting it run correctly on their platform of choice. With this release it is no difference. This time, we are hit by permission issues and wrong path settings that prohibits MySQL to start at all and also to make it automatically startup during boot time.
Fixing startup
After installing the preference pane, you should be able to simply click the button to start/stop the MySQL server. Point is that “it should”, but it wont. This is due to a wrong path setting in the startup file. In order to make it work you have to edit a file. Jump into your favorites tool (no, it is not iTunes), but the Terminal application and enter:
nano /usr/local/mysql/support-files/mysql.server
(Nano is a editor in your shell, you can also use “vi” or “emacs”, but I guess “nano” is easy to use)
Then hit “ctrl + W” (for search) and enter “basedir=”, then hit Enter”. This will search for the string entered. Once found, change it to:
basedir=/usr/local/mysql
Once changed, hit “ctrl + W” again and search for “mysqld_pid_file_path=$datadir/`hostname`.pid” and change it to:
mysqld_pid_file_path=$datadir/`/bin/hostname`.pid
After these two changes simply press “ctrl + X” and enter “y” and then enter. This will save the changes you just made and will close the editor.
Fixing Startupitem
During reboot you might have seen the error message:
“Insecure Startup Item disabled. /Library/StartupItems/MySQLCOM has not been started because it does not have the proper security settings.”
This is because the StartUpItem has been installed with the improper permission settings. This can simply be solved with the following commands you have to enter in the terminal:
chown -R root:wheel /Library/StartupItems/MySQLCOM
That’s it. After next reboot the MySQL server will startup as expected and you will also be able to start/stop the server from the preference panel.

MySQL replication - Query caused different errors on master and slave
MySQL replication works quite reliable most of the time. But from time to time, especially if you change network, servers or the master has gone away the slave will get in a "weird" state. Today, I've encountered the following error message on one of the slaves; Query caused different errors…

MySQL: Failed to open the relay log
If you happen to see the message "Failed to open the relay log..." in your MySQL error log file (sometimes it is good to look into it once in a while) then you either have your replication setup incorrectly or you forgot to remove the salve information in the master.…

MySQL: Specified key was too long; max key length is 767 bytes
I just ran into this issue while setting up a new client server with MySQL 5.6, well, Percona 5.6 in my case. It looks like one has to explicitly allow long prefixes in 5.6. Something that was never needed in 5.5 or earlier version of MySQL. In any case, adding:…

Setting the correct Java version under MacOS X
My favorite scripting language is CFML, or as some know it as ColdFusion. I like it because it is very very powerful, easy to use and can do just about everything your xyz language can do. For many years, ColdFusion was a closed sourced system, where the former Macromedia and…

Announcing Razuna 1.9.5
As outlined in my last post, Razuna is going strong, and we see that many customers take to Razuna, which after all is still one of the best open source alternatives to any Enterprise Digital Asset Management. Today, I’m thrilled to announce the immediate availability of Razuna 1.9.5. Razuna 1.9.5, despite…