Info

I got an error in the event log every time I shutdown the machine. Error 11/12/2014 9:29:58 AM Service Control Manager 7034 None Log Name: System Source: Service Control Manager Date: 11/12/2014 9:29:58 AM Event ID: 7034 Task Category: None Level: Error Keywords: Classic User: N/A Computer: DRSHD-xxxx-xxxC Description: The MongoDB service terminated unexpectedly. It has done this 1 time(s). Event Xml: 7034 0 2 0 0 0x8080000000000000 258292 System DRSHD-xxxx-xxxC MongoDB 1

Top User Comments

xgen-internal-githook commented on Fri, 9 Jan 2015 23:20:43 +0000: Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'} Message: SERVER-16106: Windows Service - Process SERVICE_CONTROL_SHUTDOWN correctly Branch: master https://github.com/mongodb/mongo/commit/dec50fa881896c0f4691df22d0017daab21e8de5 xgen-internal-githook commented on Fri, 9 Jan 2015 21:34:33 +0000: Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'} Message: SERVER-16106: Windows Service - Process SERVICE_CONTROL_SHUTDOWN correctly Branch: master https://github.com/mongodb/mongo/commit/75ca2609712b574be3b88cd40aec2ab0d8c59d0f xgen-internal-githook commented on Fri, 9 Jan 2015 21:15:49 +0000: Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'} Message: SERVER-16106: Windows Service - Process SERVICE_CONTROL_SHUTDOWN correctly Branch: master https://github.com/mongodb/mongo/commit/c81a76de0b041f1df5bd309a03f13edaa7f5c599 mark.benvenuto commented on Wed, 12 Nov 2014 22:55:01 +0000: Paul, your description of the problem is accurate. MongoD registers a Control-C handler via SetConsoleCtrlHandler. This same callback function also delivers us the Shutdown notification which causes us to shutdown even though we should wait for the SCM to signal us to stop. theonlylawislove commented on Wed, 12 Nov 2014 18:14:05 +0000: No issues with the database. I am wondering if it has to do with mongod.exe listening to a shutdown command from the operating system, instead of from the service host directly. Maybe mongod.exe is shutting down correctly on a CTRL_SHUTDOWN_EVENT, but it shutdown before the service host was going to tell it. Therefore, the service host thinks mongod.exe shutdown "unexpectedly". Just a thought. ramon.fernandez commented on Wed, 12 Nov 2014 18:09:16 +0000: Microsoft documentation indicates that this type of Event ID is caused by a service not producing a success return value on stop. However the the logs show that mongod shut down correctly: 2014-11-12T09:28:30.158-0500 CTRL_SHUTDOWN_EVENT signal 2014-11-12T09:28:30.158-0500 [consoleTerminate] got CTRL_SHUTDOWN_EVENT, will terminate after current cmd ends 2014-11-12T09:28:30.158-0500 [consoleTerminate] now exiting 2014-11-12T09:28:30.158-0500 [consoleTerminate] dbexit: 2014-11-12T09:28:30.158-0500 [consoleTerminate] shutdown: going to close listening sockets... 2014-11-12T09:28:30.158-0500 [consoleTerminate] closing listening socket: 564 2014-11-12T09:28:30.158-0500 [consoleTerminate] shutdown: going to flush diaglog... 2014-11-12T09:28:30.158-0500 [consoleTerminate] shutdown: going to close sockets... 2014-11-12T09:28:30.158-0500 [consoleTerminate] shutdown: waiting for fs preallocator... 2014-11-12T09:28:30.158-0500 [consoleTerminate] shutdown: closing all files... 2014-11-12T09:28:30.158-0500 [consoleTerminate] closeAllFiles() finished 2014-11-12T09:28:30.158-0500 [consoleTerminate] shutdown: removing fs lock... 2014-11-12T09:28:30.158-0500 [consoleTerminate] dbexit: really exiting now Is your MongoDB instance experiencing any problems? Does the issue reproduce if you stop the mongod service manually? What about if you shut down via software?

Steps to Reproduce