[SERVER-17189] Error while stopping MongoDB windows service. Created: 05/Feb/15  Updated: 11/Feb/15  Resolved: 11/Feb/15

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: 2.4.5, 2.6.7
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Narayana Mogaparti Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-16085 Windows service: net stop MongoDB giv... Closed
Participants:

 Description   

Hi,

I have installed MongoDB verison 2.4.5 / 2.6.7 on Windows 2008 R2 and registered mongod as windows service. Service is starting fine and DB working great.

When i try to stop the windows service getting below windows service error .

Windows could not stop the Mongo DB service on Local Computer.
Error 109 : The pipe has been ended.

Looks like DB is shutting down fine , here is the log

Thu Feb 05 11:27:44.735 [serviceShutdown] got SERVICE_CONTROL_STOP request from Windows Service Control Manager, will terminate after current cmd ends
Thu Feb 05 11:27:44.735 [serviceShutdown] now exiting
Thu Feb 05 11:27:44.735 dbexit:
Thu Feb 05 11:27:44.735 [serviceShutdown] shutdown: going to close listening sockets...
Thu Feb 05 11:27:44.735 [serviceShutdown] closing listening socket: 424
Thu Feb 05 11:27:44.735 [serviceShutdown] shutdown: going to flush diaglog...
Thu Feb 05 11:27:44.735 [serviceShutdown] flushing diag log
Thu Feb 05 11:27:44.735 [serviceShutdown] shutdown: going to close sockets...
Thu Feb 05 11:27:44.735 [serviceShutdown] shutdown: waiting for fs preallocator...
Thu Feb 05 11:27:44.735 [serviceShutdown] shutdown: lock for final commit...
Thu Feb 05 11:27:44.735 [serviceShutdown] shutdown: final commit...
Thu Feb 05 11:27:44.735 [conn2] end connection XX.XX.XX.XXX:xxxxx (0 connections now open)
Thu Feb 05 11:27:44.735 [serviceShutdown] shutdown: closing all files...
Thu Feb 05 11:27:44.750 [serviceShutdown] closeAllFiles() finished
Thu Feb 05 11:27:44.750 [serviceShutdown] journalCleanup...
Thu Feb 05 11:27:44.766 [serviceShutdown] removeJournalFiles
Thu Feb 05 11:27:44.782 [serviceShutdown] shutdown: removing fs lock...
Thu Feb 05 11:27:44.782 [initandlisten] now exiting
Thu Feb 05 11:27:44.782 dbexit: ; exiting immediately

When I start service back, starting fine without any errors.

I tried two versions 2.4.5 & 2.6.7, getting same error for both versions.

Thanks,
Narayana.



 Comments   
Comment by Ramon Fernandez Marina [ 11/Feb/15 ]

Thanks for your report mogaparti@gmail.com. This issue was reported earlier in SERVER-16085 and SERVER-6771, and it has been fixed in the development branch; the fix will be part of the upcoming 3.0 release.

The error message means Windows is complaining that MongoDB didn't follow the right procedure to shut down (and rightfully so), but as you've found out MongoDB does an orderly shutdown keeping your data safe. In summary, you can safely ignore the error.

Regards,
Ramón.

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