[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:
Duplicate
duplicates SERVER-2833 mongod.exe does not shut down correct... Closed
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.

----------------------------------------------
C:\>net stop mongodb
System error 109 has occurred.

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:
----------------------------------------------
C:\>net stop mongodb

The Mongo DB service was stopped successfully.
----------------------------------------------



 Comments   
Comment by Tad Marshall [ 07/Jun/12 ]

Also, see SERVER-1434 for a description that matches more closely (but is the same issue and is also fixed by SERVER-2833).

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.

Generated at Thu Feb 08 03:10:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.