-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Admin
-
None
-
Windows
-
Platform 4 06/05/15, Platform 5 06/26/16
-
(copied to CRM)
Environment:
- Cluster with 1 or more replicasets and 3 config servers, all running on Windows.
- All MongoDB processes (mongoD, mongoS, config servers) are configured as Windows services. In addition, the services are setup with recovery actions that cause Windows to restart them on failure.
- mongoS and config servers run on different hosts.
Scenario:
- Hosts are restarted.
- mongoS Windows service starts before the config servers Windows services start.
- mongoS service stops because it can't connect to any config servers.
- However, Windows does NOT restart it - i.e., the recovery actions don't work.
I believe that the issue is caused by method initService() in ntservice.cpp unconditionally calling reportStatus(SERVICE_STOPPED) when the service callback method returns.
Here's a tentative fix:
https://github.com/mongodb/mongo/pull/925
- duplicates
-
SERVER-6771 Windows Service: 'net stop mongodb' gives System error 109 has occurred. -- The pipe has been ended.
- Closed
-
SERVER-13338 NT Service does not return failure code on exit
- Closed
-
SERVER-16085 Windows service: net stop MongoDB gives an error even after stopping the service
- Closed
- related to
-
SERVER-21019 MongoS service does not restart as per service defined behaviour if all config servers are down
- Closed
- links to