MySQL Bugs: #28628: Config Wizard can't connect (race condition)

Bug #28628	Config Wizard can't connect (race condition)
Submitted:	23 May 2007 17:40	Modified:	26 Feb 2008 10:04
Reporter:	Olaf van der Spek (Basic Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S3 (Non-critical)
Version:	5.1.18,,5.1.21, 6.0.0	OS:	Windows
Assigned to:	Iggy Galarza	CPU Architecture:	Any
Tags:	qc

Description:
Hi,

While installing 5.1.18 and 6.0.0, I encountered the following error:
Connection Error
The security settings could not be aplpied to the database because the connection has failed with the following error.

Error Nr. 2003
Can't connect to MySQL server on 'localhost' (10061)

If a personal firewall ...

If you are re-installing ...

Retry | Skip

When I click Retry, it continues without error.
So I think there's a race condition and the server isn't ready yet when the wizard tried to connect.

This may be related to dual-core / dual-socket systems.

How to repeat:
Install.

i suspect innodb log files are being written which takes some time and during that time service is 'started' by mysql doesn't accept tcp connections yet. just a thought.

Thank you for a problem report. Please, send my.ini file that was used/generated.

my.ini

Attachment: my.ini (application/octet-stream, text), 8.87 KiB.

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".

Hmm, I did upload my my.ini a month ago. A bug in the bug tracker?

Thank you for the feedback.

I can not repeat described behaviour with MySQL 5.1.19

Please upgrade and try with new version and if you can repeat indicate if you have firewall and every setting you set up in the Configuration Wizard.

I've repeated this today with 5.1.19 in a Windows XP setup on VMware Workstation.
No firewall, all defaults in the config wizard.

Doesn't the Windows Service Control Manager provide a way to check whether the service is fully running?

Tested multiple installations of the 4.1 and 5.0.52 .msi files without incident.

Noted that there is a variable (5-30 seconds -- depending on machine load) when a user enters an incorrect, existing password when trying to change security settings during configuration.  However, this seems minor and an acceptable tradeoff to fix the bug.

Ok to push.

Marked bug#20069 a duplicate.

A note has been add to the 5.1.23, 5.0.51a and 6.0.5 changelogs: 

When running the MySQL Instance Configuration Wizard, a race condition could exist that would fail to connect to a newly configured instance. This was because mysqld had not completed the startup process before the next stage of the installation process.

To the changelog? Shouldn't it at least go in the readme?

Still, this is not a (proper) solution.