Bug #59236 OSX installation fails to set basedir

• Submitted: 30 Dec 2010 22:40
• Modified: 9 Mar 2011 15:52
• Reporter: Robert Freund
• Status: No Feedback
• Category: MySQL Server: Installing
• Severity: S3 (Non-critical)
• Version: 5.5.8
• OS: MacOS (10.6-x86_64)
• CPU Architecture: Any

[30 Dec 2010 22:40] Robert Freund

Description:
After installing the MySQL pkg and StartupItem pkg, the MySQL service refuses to start.  It turns out that at startup mysql.server was not resolving the basedir.  The solution in this case was to add a /etc/my.cnf file with the following content:

[mysqld]
basedir=/usr/local/mysql

This was not described anywhere in the readme and should probably be performed automatically by the installer.

How to repeat:
Intall the MySQL and StartupItem packages using their related installers.  Type the following command, as indicated in the installation instructions:

sudo /Library/StartupItems/MySQLCOM/MySQLCOM start

Note that this did NOT start MySQL.

Suggested fix:
The workaround is to manually add /etc/my.cnf with the following content:

[mysqld]
basedir=/usr/local/mysql

The correct fix would be to have the installer perform this action or set basedir in some other acceptable fashion.

[25 Jan 2011 18:18] Valeriy Kravchuk

Looks like a duplicate of bug #51264. Please, check.

[30 Jan 2011 11:39] Robert Freund

I don't believe this is a duplicate of 51264 as it does not cause an error in the installation of the preference pane.  Rather, everything appears to install OK, but the MySQL start/stop button does nothing.

[30 Jan 2011 12:07] Valeriy Kravchuk

Well, fix for that bug (see http://lists.mysql.com/commits/127231) is related to proper setting of basedir, and (based on the information you provided and numerous duplicates) setting basedir properly solves the problem reported here.

[30 Jan 2011 12:10] Robert Freund

The basedir information is in the original bug.  That operation should either be documented, or fixed in the installer.

[9 Feb 2011 15:52] Valeriy Kravchuk

Please, check if version 5.5.9 solves the problem for you.

[10 Mar 2011 0:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".