Description:
If server fails to start as a service during instance configuration/startup on Processing configuration/Start service step, Config Wizard does not report the failure, but instead just keeps waiting forever, and eventually has to be killed.
The effect appears starting from version 5.1.38. In 5.1.37 the wizard promptly throws the error.
Possibly the difference came along with the new version of Config Wizard (1.0.16.0 in 5.1.38 vs 1.0.15.0 in 5.1.37). Alternatively, there were some other installation-related changes in 5.1.38 which could affect the behavior.
Please note that the complaint is not about service not being started, the reason for it is clear (in the test case below it would be InnoDB log file size mismatch); the problem is that startup failure is not recognized by Config Wizard.
How to repeat:
In a fresh environment, without data folder in default location,
- install server from an msi package (Typical setup is enough);
- run Config Wizard;
- accept all defaults in Config Wizard, including 'Developer Machine' in the server type screen;
- wait till service is started;
- run Config Wizard again;
- choose 'remove instance' and proceed;
- run Config Wizard for the 3rd time to create a new instance;
- accept all defaults except for the server type screen -- there choose 'Server Machine' instead (it should make Config Wizard set different value of innodb_log_file_size);
- finish configuration and see that Config Wizard hangs on 'Start Service' step;
- check server error log file to see that it attempted to start and was shut down;
- check Windows Event Viewer to see that startup failure is reported there.
Suggested fix:
Make Config Wizard recognize and report failure. While it causes complaints since the diagnostics is not clear, it is still better than the hang up.
