MySQL Bugs: #28128: Administrator BROKE my MySQL installation in OS X Server

Bug #28128	Administrator BROKE my MySQL installation in OS X Server
Submitted:	27 Apr 2007 1:17	Modified:	26 May 13:55
Reporter:	Rob Lewis (Candidate Quality Contributor)
Status:	Unsupported
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.2.11	OS:	Mac OS X (Server 10.4.9)
Assigned to:		Target Version:
Tags:	privileges, logging, administrator, os x, server
Triage:	D3 (Medium)

Description:
I attempted to use MySQL Administrator to stop the MySQL server. I wanted to restart it
in the hope it would make logging work (I had used Aministrator to enable some logging).

Administrator gave me a message "unable to stop the server". Later I discovered that the
server actually was stopped and COULD NOT BE RESTARTED! 
Administrator and all my other programs give a message that they can't connect to the
server. In OS X Activity Monitor, I don't see a "mysqld" process running. I can't find
mysqld to try to run it. 
Note that OS X Server uses a nonstandard socket to connect: /var/mysql/mysql.sock, but I
have this configured properly in all my programs. 
Amazingly, the /etc/hostconfig file now has a line that says
MYSQL=-NO-
When it used to say MYSQL=-YES-
Every time I try to change it to -YES-, SOMETHING keeps changing it back to -NO-!
Help, please! 

How to repeat:
In OS X Server 10.4.9, use Administrator to attempt to stop and restart the MySQL server.

Suggested fix:
Please make Administrator recognize any special configuration needs of OS X AND OS X
Server and respect them. Please do not let it destroy an installation of MySQL!

Oops, my bad. When I enabled the logging options, I neglected to give MySQL write
privileges for the folder I told it to write the logs in. After doing that it seems to be
back in business. 

Still, it was rather bad form for MySQL to simply refuse to start up with no error
message of any kind. And it would have been REALLY NICE if Administrator had checked to
be sure it was able to write the files!

Thank you for the report.

In the last comment you says it is not really bug, but first part of the report is bug:

After click on "Stop server" button Administrator gave a message "unable to stop the
server", although server is really stopped. After MySQL Administrator shows message
"MySQL server is running", although it is not running.

So I marked the report as "Verified".

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/27450

ChangeSet@1.2502, 2007-05-28 15:33:22+04:00, kaa@polly.local +3 -0
  Some Windows-related fixes to make Microsoft compilers happy. This is for bug #28128.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/27671

ChangeSet@1.2505, 2007-05-30 15:14:21+04:00, kaa@polly.local +3 -0
  Got rid of log_01[], because we don't really need it. Division and log_10[] can always
be used instead, which is also a more precise way.
  
  This is for bug #28128.

Pushed into 5.1.20-beta

Pushed into 5.0.44

Many thanks for writing a bug report. We are on the way to implement full functionality of
MySQL Administrator into MySQL Workbench. Unfortunately you are using an unsupported
platform. More informations about supported platforms you will find here:

http://www.mysql.com/support/supportedplatforms/tools.html

More informations about MySQL Workbench you will find here:

http://dev.mysql.com/workbench/