Bug #45546 | Start windows service, then execute what is needed. | ||
---|---|---|---|
Submitted: | 17 Jun 2009 5:19 | Modified: | 15 Dec 2011 18:41 |
Reporter: | Roel Van de Paar | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Windows | Severity: | S2 (Serious) |
Version: | OS: | Windows | |
Assigned to: | CPU Architecture: | Any |
[17 Jun 2009 5:19]
Roel Van de Paar
[17 Jun 2009 5:48]
Sveta Smirnova
Potentially can lead to same problem as in bug #41908
[17 Jun 2009 19:43]
Valeriy Kravchuk
Windows should not let to start service that is already started/is in the process of starting. I think this is a reasonable feature request.
[12 Oct 2009 2:02]
Roel Van de Paar
If the server is slow in shutting down, possibly the same issue may happen during shutdown. Workaround: use: shell> SC INTERROGATE <service_name> | FIND "STATE" To check if the service has successfully started/stopped. Example: --------- C:\>NET START mysql5137 The mysql5137 service is starting. The mysql5137 service was started successfully. C:\>SC INTERROGATE mysql5137 | FIND "STATE" STATE : 4 RUNNING C:\>NET STOP mysql5137 The mysql5137 service is stopping. The mysql5137 service was stopped successfully. C:\>SC INTERROGATE mysql5137 | FIND "STATE" C:\> ---------
[15 Dec 2011 18:41]
Paul DuBois
Noted in 5.5.20, 5.6.5 changelogs. A new server option, --slow-start-timeout, controls the Windows service control manager's service start timeout. The value is the maximum number of milliseconds that the service control manager waits before trying to kill the MySQL service during startup. The default value is 15000 (15 seconds). If the MySQL service takes too long to start, you may need to increase this value. A value of 0 means there is no timeout.