MySQL Bugs: #60361: registered service from previous version not working in 5.2.32

Bug #60361	registered service from previous version not working in 5.2.32
Submitted:	6 Mar 2011 13:02	Modified:	7 Jun 2011 15:20
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.32	OS:	Windows (7/64)
Assigned to:		CPU Architecture:	Any
Tags:	qc

Description:
I have both MySQL 5.0, 5.1 and 5.5 installed as services.

details: 
5.0 is listening on port 3309. Service name is 'mysql50'. This service is started manually.
5.1 is listening on port 3306. Service name is 'mysql51'. This service is started at OS startup.
5.5 is listening on port 3307. Service name is 'mysql55'. This service is started at OS startup.

(all the servers listed above are 64bit Win servers installed with the automatic installers. I also have a MariaDB isntance and an InfiniDB instance - but I believe not relevant here.)

From a previous WB build (probably 5.2.31 - but not perfectly sure) I had registered the 5.1 instance in WB (it worked basically - only crashed every 5-10 minutes as WB consistently does). After upgrade to 5.2.32 I cannot connect to the 5.1 instance anymore.  I first thought it tries to connect to the 5.0 instance that is not running and thus returns 'cannot connect'. However starting the 5.0 instance manually (thus activating a server on port 3306) changes nothing. Still 'can't connect'

I deleted the 5.1 instance from the list of registered servers in WB, but cannot create it again as it still cannot connect and I cannot proceed in the wizard beyond that point.

I can connect to the 5.5 instance. 'root' password is same on all instances - though probably not relevant is this a a *connection* error and not an *authentication* error.

How to repeat:
see above

Suggested fix:
no idea.

connection settings

Attachment: settings.jpg (image/jpeg, text), 27.67 KiB.

can't continue from here

Attachment: failure.jpg (image/jpeg, text), 29.46 KiB.

corrected version no. in synopsis.

A mistake in my frist post!

Please discard "(thus activating a server on port 3306)".  5.1 is running and is listening on port 3306. I can connect with command line client and SQLyog.

I can also connect to the 5.0 instance on port 3309 (when service has been started). But still not to the 5.1 instance on port 3306.

I was able to register and connect this morning. But this is crazy: I specify the port 3306. After that it presents me for a list of 'localhost' servers. Why?  There is only one running on port 3306. I have decided which one I want to connect to!! Anyway I chose the 5.0 instance (just to see what would happen) and it did *overwrite* the 5.1 instance that I created successfully 2 minutes before.

Hi Peter,
could you reproduce the problem that WB wouldnt connect to one of your instances, or does it work now (after your numerous tries)?
You're talking about Administration instances, right?
thanks in advance

My *point* is that as I have already specified both host and port, it is *insane* that WB asks me to choose an instance to manage. There is only one instance 'satifying' the conditions: host = x and port = y.

My *point* is that as I have already specified both host and port, it is *insane* that WB asks me to choose an instance to manage. There is only one instance 'satifying' the conditions: host = x and port = y.

Additionally: as the situation is not reproducible (ie. the upgrade to 5.2.33 cannot be repeated as it is only possible to do once) I think it is very difficult to spot the original problem I had if it is related to this upgrade.

I also posted another report with server management issue with my setup (3-4 64bit localhost servers on Windows).  They may be two different incarnations of the same devil!

What remains however is that as I specify both host and port, there is no reason to popup a dialog where I select the server afterwards.  I already have done by specifying both host and port. So we can 'reduce' this report to this if you prefer (In that case just rewrite the synopsis as per your taste).

Thank you for the feedback. If I understand the original bug report isn't more repeatable but now limited in the unnecessary dialog box?. Thanks.

I am sorry, but I really do not have an option to 'roll back' now. What exactly do you think I could or should do?

Bug Closed as per previous reporter comment.
This defect is not reproducible anymore.
For the "Create New Server Instance" phenomenal, where the application ask for the service data on "Database connection" and "windows management" steps, will be consider as an improvement.
Thanks a lot for your report.