Bug #2848 If the mysql service fails to start, administrator doesn't seem to notice
Submitted: 17 Feb 2004 15:43 Modified: 11 Mar 2004 8:31
Reporter: Harrison Fisk Email Updates:
Status: Closed Impact on me:
Category:MySQL Administrator Severity:S3 (Non-critical)
Version: OS:Windows (Windows XP)
Assigned to: Michael G. Zinner CPU Architecture:Any

[17 Feb 2004 15:43] Harrison Fisk
If you try to start the service from Service Control, but the MySQL service fails to start for some reason (bad config file, etc...) then MySQL Administrator never reports it.  

It instead will look like it is still trying to start it forever, with the little status bar cycling and the last message in the log as "Trying to start the server..."

How to repeat:
Put a bad option inside of a configuration file.
Try to start the service from inside of MySQL Administrator.
Watch the little cycling thing forever.

Suggested fix:
MySQL Administrator should report that the service couldn't be started for some reason.  Obviously if it could get the reason that would be better, but even saying it failed would be a good start.
[11 Mar 2004 8:31] Michael G. Zinner
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at