MySQL Bugs: #7900: Unable to manage two MySQL Servers running on the same machine as service.

Bug #7900	Unable to manage two MySQL Servers running on the same machine as service.
Submitted:	14 Jan 2005 9:52	Modified:	19 Jan 2005 20:41
Reporter:	Benjamin Wilger	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.0.19	OS:	Windows (Windows 2003 Server)
Assigned to:		CPU Architecture:	Any

Description:
We've got two MySQL Servers installed on our Windows 2003 Server. The first is a 3.3.27er running on port 3306 and the other's Version is 4.1.7 running on port 3307. Both are registered as a service on the machine and start automatically.

Regardless which server I connect on (3306, 3307) MySQL Administrator always uses the first service in the services list to get information where the my.ini is located.

This leads to some critical issues: Changing then the configuration of the selected server will change the configs of the other server, but access to data is done at the right server.

Please excuse my bad english.

How to repeat:
Install two MySQL Servers (i.e. 4.1.7) on different ports on the same machine and register them as services. After that try to configure both servers with the Administrator.

Suggested fix:
If MySQL Admin determines two or more Services matching "mysql*" give the user the chance to choose the right service on it's own.

Even newer versions (1.0.19) have this issue. Sorry.

Changed severity of this report because it is in my opinion actually a bug, not a missing feature.

Thanks for reporting. There is a known issue that it is impossible to tell which .ini / .cnf is used when multible server instances are installed on one machine.

There are two solutions to handling multible server installations with MySQL Administrator. Both solutions only work if you have installed MySQL to run as a service and use the --defaults-file option. This is done automatically by the Configuration Wizard for 4.1 and 5.0 servers.

Please check your HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MySQL Key in the registry. A typical [ImagePath] should look like this.
"C:\Programme\MySQL\MySQL Server 4.1\bin\mysqld-nt" --defaults-file="C:\Programme\MySQL\MySQL Server 4.1\my.ini" MySQL41

The first is, to hold the [Ctrl] key in the Connection Dialog. This will change the [Cancel] button to [Skip]. When the [Skip] button is pressed, the connection to the server is skipped and you enter the instance configuration mode. You are able to see all installed instances and the config files are displayed correctly.

The second is, to use the MySQL System Tray Monitor and select to configure an instance there. This will also make sure the correct .ini / .cnf file is read.

This bug is not scheduled to be fixed at this time.