[SERVER-6040] Stopping the mongod Windows Service Results In Error Message Created: 07/Jun/12 Updated: 07/Jun/12 Resolved: 07/Jun/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.0.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Ryan Hoffman | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows Server 2008 R2, using 2.0.6 x64 2008+ Build |
||
| Issue Links: |
|
||||||||
| Operating System: | Windows | ||||||||
| Participants: | |||||||||
| Description |
|
Sometimes, when issuing a stop command to the MongoDB Windows Service, mongod does not exit cleanly and throws an error. ---------------------------------------------- The pipe has been ended. Is this even alright to exit this way? Should I look for DB corruption or anything else? This is the expected output: The Mongo DB service was stopped successfully. |
| Comments |
| Comment by Tad Marshall [ 07/Jun/12 ] |
|
Also, see |
| Comment by Tad Marshall [ 07/Jun/12 ] |
|
This is fixed in version 2.1.0. We weren't doing the right shutdown sequence, depending on the order of notifications we got. "net stop mongodb" is the preferred way to shut down mongod.exe when it is running as a service because this way the Windows Service Controller doesn't see an unexpected shutdown, but it didn't always produce clean exits in versions prior to 2.1.0. |