MySQL Bugs: #5186: Administrator : Unwanted Disconnection

Bug #5186	Administrator : Unwanted Disconnection
Submitted:	24 Aug 2004 17:50	Modified:	12 Jul 2005 22:46
Reporter:	Andreas Mackensen	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.0.10 (originally 1.0.9)	OS:	NT4.0, W2K
Assigned to:	Vladimir Kolesnikov	CPU Architecture:	Any

Description:
When connected to a remote machine, i.e. non-localhost, the connection automatically is closed after clicking on Service Control.

- The server (MySQL 4.0.20-max-log) runs on a Sun Fire V120 with Solaris 8.
- The client is installed on an NT4.0 PC, with an IP address in the same network segment.
- On the client machine, another server is installed and registered as a service (manual start), which by default is stopped.
- Connection is over default port 3306.
- I'm logging in as root, password set, having all rights and GRANT privilege for all databases/schemas on the server.
- Administrator has been installed in the no-installer version.
- I'm opening the tool, logging in to the remote server, and have all functions active except for Service Control and Startup Variables. I then can click on any category and can use the respective GUIs normally.
- When clicking on Startup Variables, I get the hint that this option is available only for localhost, and then can choose any other category, continuing the session.
- When clicking on Service Control, though, I first see the greyed-out GUI, which then suddenly seems to become active, i.e. switches to normal colours, and the message that the service is stopped. At this point, all other options become unavailable, and the connection to the remote host is lost.

I've been able to reproduce the behaviour under W2K as well, on my notebook from another IP address. In both cases, with MySQL locally installed as a service (--install-manual) I found out something else:

- If the local service is stopped, my problem regularly turns up.
- If the local service is started, the problem does not occur.

I've also made another test: remove the local service (mysqld-nt --remove), and then connect to the remote server. Now the connection is not closed when clicking on Service Control, but Server Logs shows me the local log files -- although it says "This section is only available when connected to localhost".

Note: This bug has been opened as customer support issue #3323 already -- that's where the above text originally comes from; more details can be found in the customer support database. I am considering to replace MySQLCC -- which doesn't seem to be in the tool family anymore -- with both Administrator and QueryBrowser, which makes the matter rather important to me.

How to repeat:
cf. description above

Thank you for the detailed bug report. The issue will be addressed a.s.a.p. and the fix will be in the next MA release. I will upload an internal release tomorrow and will ask you to verify the fix on your system.

By the end of the month we will release the Beta version of Query Browser. This Beta version of QB will, together with MA, contain the full functionality needed to replace MySQL CC.

This bug is now fixed. I have created an internal release 1.0.10.2. Please download this release from 

ftp://ftp.mysql.com:/pub/mysql/download/mysql_administrator_gpl.msi

I would ask you to close the bug report if it addresses the issue on your systems, too.

I've tested the provided bug fix (1.0.10.2), and found that the the problem does not exist any longer. Please close the bug report.

Please upgrade to the official release 1.0.11, which also addresses a bug in the table editor.

The problem is re-occuring with Administrator 1.0.12. Seems the fix included in 1.0.11 hasn't been used this time round.

Reopened for more testing

Varified with version 1.0.12
Disconnection occurs if I connect to the local MySQL server and have another  MySQL server installed and registered as a service.
If I connect to the remote MySQL server, I just get an error message: "This section is only available when connected to localhost"

When you click on the Service control section it appears to look for a service who's executable name (not service name) starts with "MySQL" i.e. mysqld-nt.exe.  

In the configuration below if the administrator is connected to V5 (MySQL Version 5.0) then it may "find" the V4 service and it will display both it's Service Control Status and V4s Startup Variables.  If the V4 service is not running you will get disconnected.  

To avoid getting accidentally disconnected you can rename the executables such that they do not start with "MySQL" i.e. my4sqld-nt.exe and my5sqld-nt.exe and set the services to run these.  The downside to this is that neither the "Service Control" or "Startup Variables" sections of Administrator will be operable since Administrator will not "find" the service.  This obviously could also be achieved by never clicking on either section so it is of limited use as a workaround.  Hopefully this information will help in the diagnosis of the problem though.

Notes:
Renaming the executables to mysqld-nt4.exe and mysqld-nt5.exe does not work since they both still start with "mysql" and you have the same problem.
Changing just the service name to differentiate them does not help either.

MySQL Administrator:  1.0.21
OS: XP Pro SP2
MySQL: Versions 4.1.12a-nt and 5.0.7-beta-nt running locally as service.

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
    http://www.mysql.com/doc/en/Installing_source_tree.html