-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 2.0.7, 2.2.0-rc1
-
Component/s: Packaging
-
Environment:Windows, mongod.exe or mongos.exe running as a service
-
Fully Compatible
-
Windows
-
Server 2.7.5
-
(copied to CRM)
When mongod.exe is installed as a service on Windows (with --install), the "net stop mongodb" command does not reply with "The Mongo DB service was stopped successfully." the way it did in version 2.1.0 but instead displays "System error 109 has occurred." and "The pipe has been ended.". This was likely broken by changes we made to our exit logic after 2.1.0 but before 2.2.0-rc1.
This error message is actually the extent of the problem – we shut down cleanly and no errors are logged in the Windows Event Log.
- is duplicated by
-
SERVER-7901 mongo services on stopping gives Error 109 : Pipe has been ended
- Closed
-
SERVER-17295 On Windows, service recovery actions don't work is mongoS fails to initialize
- Closed
-
SERVER-16085 Windows service: net stop MongoDB gives an error even after stopping the service
- Closed
- is related to
-
SERVER-5703 ntservice should not have to fake out exitCleanly() to achieve its ends
- Closed
- related to
-
SERVER-6065 db.shutdownServer() does not work as expected when mongod is a Windows Service
- Closed
-
SERVER-12875 Service doesn't stop cleanly on Windows
- Closed