MySQL Bugs: #30525: Server instance configuration wizard

Bug #30525	Server instance configuration wizard
Submitted:	21 Aug 2007 1:22	Modified:	17 Aug 2009 16:39
Reporter:	Bob Florian	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S2 (Serious)
Version:	5.x, 5.0.77, 5.1.31, 5.1.32	OS:	Any
Assigned to:	Iggy Galarza	CPU Architecture:	Any
Tags:	inconvienence

Description:
When installing the server with a GUI, and using the instance configuration wizard, when you finally "execute" all of the configured parameters, the installer gives a red 'x' to starting the server and connecting to it.  It then gives you the option to retry.  Retrying will always work.  Installer program is not waiting long enough for the service to start before attempting to connect to it.

How to repeat:
Install mysql with the GUI installer, and follow all instructions.  Server instance configuration wizard will fail periodically, and not connect to the new instance.

Suggested fix:
Wait longer for service to start.

Thank you for the bug report.

I'm encountering the exact same issue.

Any other solutions aside from waiting U& retrying to execute?

In 5.1.31 and 5.0.77 situation looks even worse: configuration wizard doesn't wait enough for MySQL service to start and reports 'Could not start MySQL' - looks that installation failed. In addition it doesn't ask for retry and doesn't apply secure settings (doesn't change root password and doesn't remove anonymous login).

Some MySQL experience required to understand that user needs to use empty root password (even if new password was defined in installation process) or re-run configuration wizard.

Please retriage because the fix should be simple (just increase timeout) and installation looks completely failing while everything gets installed properly (except securing password, etc)

I ve just add the exact same problem using mysql-5.1.34-win32.msi or mysql-5.1.35-win32.msi as an install. Install is fine but this is when configuration starts up (mysql server instance configuration wizard 1.0.15.0) and try to run MySQL service that it fails at the very beginning .
Here are the choices I did in the wizard 
checked detailed configuration
checked developer machine 
checked  multifunctionnal databse
choosed some folder for innoDB (actually d:\MySQL\)
checked manual settings (15 conections)
checked enable TCP/IP port # 3306
checked add firewall exception 
checked enable strict mode
checked  std char set
checked install as windows service 
checked lanch auto
checked include bin dir in windows path
unckeched security seetings (empty passwords)
Pressed execute and finally failed @ "start service" 
Pressed canceled 
opened services Microsoft Corporation  Version : 5.1.2600.0 (windows XP)
started MySQL service manually
opened the debugger in myslqld.exe which hanged in _callthreadstart() somewhere 
in g:\mysql-5.1.34-winbuild\mysql-community-nt-5.1.34-build\sql\mysqld.cc
after a call to init_server_components() (from ASM code)

What 's weird is that last week I could succeed the install w mysql-5.1.34-win32.msi 
I'm wondering if this is not related with microsoft recent updates messing up with the service.

Extend exisitng 30 second timeout to 1 minute.

Attachment: bug30525.patch (application/octet-stream, text), 751 bytes.

Performed multiple installs / removal + reinstalls and some upgrades (5.1.35-> 5.1.36).
Was unable to encounter this bug with the test .msi.  I was hitting the bug with some regularity with 5.1.35's .msi.

Ok to push.

A note has been added to the 5.1.38, 5.4.2, 5.0.85, 4.1.26: 

When performing an installation on Windows using the GUI installer, the installer would fail to wait long enough during installation for the MySQL service to be installed, which would cause the installation to fail and may cause security settings, such as the root password to not be applied correctly.