MySQL Bugs: #59558: "make sure you have opened TCP port 3306" doesn't reflect ACTUAL port on install

Bug #59558	"make sure you have opened TCP port 3306" doesn't reflect ACTUAL port on install
Submitted:	17 Jan 2011 16:17	Modified:	4 Mar 2013 17:03
Reporter:	ivan jefton	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S3 (Non-critical)
Version:	5.5.8	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
when installing not using the standard port 3306, and getting an error when applying the standard security settings (that's a different bug), the alert dialog box doesn't display the actual port mysqld is using; instead it displays the default port of 3306.

How to repeat:
install mysql (using the windows installer); select a non-standard port on the "Enable TCP/IP Networking" page; select the "Enable Root access from remote machines" checkbox on the "Modify Security Settings" page (this will cause an error, due to the authorization_string NOT NULL without default bug). After clicking EXECUTE (on the next page), the install process will fail with an error "the security settings could not be applied to the database because the connection has failed with the following error...". Note the port number is 3306, NOT the port number previously configured.

Suggested fix:
pick up the port number configured during the install instead of displaying the default port number of 3306.

security settings error message showing default port number

Attachment: mysql_port3306.PNG (image/png, text), 15.92 KiB.

the "different bug" i refer to is bug 59038.

What exact Windows version, 32-bit or 64-bit, do you use? Is it a new installation or upgrade?

I've tried to install 5.5.8 over older 5.5.7 on 64-bit XP, and got correct non-default port used, 3308, in the Connection Error dialog box.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Not enough information to reproduce. Bug has been open for two years, and we
are thus assuming that this issue is no longer current.