Bug #51146 MySQL Workbench incorrectly reports that server is stopped

• Submitted: 12 Feb 2010 14:29
• Modified: 15 Nov 2011 4:03
• Reporter: chris rowland
• Status: Closed
• Category: MySQL Workbench: Administration
• Severity: S4 (Feature request)
• Version: MySQL Workbench version 5.2.15 OSS Beta
• OS: Windows
• CPU Architecture: Any

[12 Feb 2010 14:29] chris rowland

Description:
MySQL Workbench version 5.2.15 OSS Beta Revision 5053
MySQL Server version: 5.1.43-community MySQL Community Server (GPL)
Windows XP Service Pack 3

Connecting to server on localhost.

The server is running, and the SQL Editor works

However, Admin says the server is not running. Trying to start the server displays
2010-02-11 09:41:07 - Checked server status: Server is stopped.

2010-02-11 09:41:07 - Trying to start server...

2010-02-11 09:41:12 -

2010-02-11 09:41:12 - Checked server status: Server is stopped.

How to repeat:
Create a connection.
Use that connection to do a query & it succeeds.
Use that connection to perform server administration and the server will appear stopped.

[12 Feb 2010 16:45] MySQL Verification Team

I couldn't repeat this issue on Vista Ultimate X64.

[12 Feb 2010 17:14] Valeriy Kravchuk

What Windows service name does your MySQL server have? Is it MySQL or something else, MySQL51 maybe?

[12 Feb 2010 19:46] chris rowland

The name of the service is "MySQL5.1"

[13 Feb 2010 7:22] Valeriy Kravchuk

Please, check if service name is set accordingly for the instance (Manage Server Instances > System Profile tab > MySQL Management tab and Check MySQL Status field) then.

[15 Feb 2010 16:14] chris rowland

Changing the 'Check MySQL Status:' field from
"sc query mysql| wba_filter(RUNNING)"
to
"sc query MySQL5.1| wba_filter(RUNNING)"
fixed the problem.

[19 Feb 2010 10:51] MySQL Verification Team

Thank you for the feedback. Please try version 5.2.16 and comment the results here. Thanks in advance.

[19 Feb 2010 14:12] chris rowland

Version 5.2.16 doesn't really fix the issue, you still need to modify the service name in the "Check MySQL Status" field to make it work.

[21 Feb 2010 18:45] Valeriy Kravchuk

So, this is more like a feature request: WB should find out/guess associated service name from the registry, based on profile/installation type selected. 

Do you agree?

[22 Feb 2010 14:15] chris rowland

Yes, now that I know how to modify the configuration to work, it sounds more like an enhancement than a bug.  In the short term maybe the description should document that the name used must match the service name.

[22 Feb 2010 14:16] chris rowland

Changed to feature request

[15 Nov 2011 4:03] Philip Olson

Fixed as of 5.2.33:
+        &workbench; would incorrectly report that the MySQL server had
+        stopped.