MySQL Bugs: #48975: MySQL Workbench administrator does not detect server status correctly

Bug #48975	MySQL Workbench administrator does not detect server status correctly
Submitted:	23 Nov 2009 5:55	Modified:	15 Feb 2010 11:53
Reporter:	Giuseppe Maxia	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S1 (Critical)
Version:	5.2.8, 5.2.10	OS:	MacOS
Assigned to:	Maksym Yehorov	CPU Architecture:	Any
Tags:	administrator, detection, server, STATUS, workbench

Description:
When more than one MySQL server is running on the same host, the server detection fails to detect if the server is not running.

If it not running, it wrongly says that it's running. After stopping the server, it reports success on the operation, but still reports the server as running.

How to repeat:
1a. Use MySQL Sandbox to start a new server.
1b. Stop the main server
1c. Use MySQL Workbench administrator interface

2a. Start the MySQL test suite
2b. stop the main server
2c. Use MySQL Workbench administrator interface

Suggested fix:
Make Workbench detect if the server is running with the same procedure used by the mysql.server script.
Tell the users what output a start/stop script should produce (i.e. what MySQL Workbench expects to see when the server is on or off), so they can create their own scripts.

we need to document the commands/scripts WB uses for start/stop/status so users can build their own scripts

Giuseppe,

mysql.server script doesn't work for me:

kojima@Peppermint wb52$ /usr/local/mysql/support-files/mysql.server status
/usr/local/mysql/support-files/mysql.server: line 418: pidof: command not found
 ERROR! MySQL is not running

Does it work in your Mac?

Alfredo: it works for me

$ sudo /usr/local/mysql/support-files/mysql.server status
 SUCCESS! MySQL running (18956)
$ sudo /usr/local/mysql/support-files/mysql.server stop
Shutting down MySQL
. SUCCESS! 
$ sudo /usr/local/mysql/support-files/mysql.server status
 ERROR! MySQL is not running
$ sudo /usr/local/mysql/support-files/mysql.server start
Starting MySQL
. SUCCESS! 
$ sudo /usr/local/mysql/support-files/mysql.server status
 SUCCESS! MySQL running (19077)

pidof doesn't seem to be installed in our Snow Leopard build server either.
Can you do a "type -a pidof" and see where it's coming from? I suspect it might be from something
like fink or macports.

pidof is not installed in my box. Yet, the script works as expected. If pidof doesn't return a valid value, then the script looks for the lockfile, and uses it to determine if the server is running.

If Workbench documents what each script should do, it would be easy for users to build their own.

For example:

* START 
  ** action : starts the server
  ** returns: 0 on success, -1 on failure
  ** prints : optional debugging info to STDOUT

* STOP 
  ** action : stops the server
  ** returns: 0 on success, -1 on failure
  ** prints : optional debugging info to STDOUT

* STATUS
  ** action : none
  ** returns: 0 on server running, 1 on server stopped, -1 on error
  ** prints : optional debugging info to STDOUT

Good point. Because even if the start/stop script works, it would help with this bug if they work on the same instance.

I'll add a small window with better description for what to put in the options and also ask it to be put
on the full WB documentation.

Changed the default command to check for status to:

ps xa | grep /usr/local/mysql/bin/[m]ysqld

This will allow distinguishing different server versions by their installation paths.

fix will be included in 5.2.16

Would it be possible to include an explanation of what Workbench expects the scripts to return?

This way, users could create their own custom commands for starting, stopping, and querying the status.

Thanks.

Giuseppe has a valid point here. Please add a description of what means "success" and what means "failure" to the Filter Help dialog.

Currently, the dialog just states what you can use. But it does not state how to actually make it work.

Also, please add an example of how to use the filters.

Added explanation to server instance editor.

description of the commands has been added to the "filters help" dialog

An entry has been added to the 5.2.16 changelog:

MySQL Workbench did not correctly detect the status of MySQL Servers where multiple servers were running on the same host, and so displayed incorrect server status on the Admin screen.