[SERVER-1434] "Net stop mondodb" returns an error on windows. Created: 18/Jul/10 Updated: 12/Jul/16 Resolved: 15/Mar/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools, Usability |
| Affects Version/s: | 1.5.5 |
| Fix Version/s: | 1.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Justin Dearing | Assignee: | Tad Marshall |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 7 64bit |
||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
This is from a POST 1.55 daily build. If I type net stop mongodb from the command line I get: The pipe has been ended. The log says this: The long version of what I did. C:\Program Files\10gen\mongodb-win32-x86_64-2010-07-17\bin>mongod --reinstall --logpath "c:\data\logs\mongo.log" C:\Program Files\10gen\mongodb-win32-x86_64-2010-07-17\bin> The Mongo DB service was started successfully. C:\Program Files\10gen\mongodb-win32-x86_64-2010-07-17\bin>net stop mongodb The pipe has been ended. C:\Program Files\10gen\mongodb-win32-x86_64-2010-07-17\bin>type c:\data\logs\mongo.log [initandlisten] Sun Jul 18 01:12:18 select() failure: ret=-1 errno:10038 An operation was attempted on something that is not a socket. [initandlisten] Sun Jul 18 01:12:18 now exiting C:\Program Files\10gen\mongodb-win32-x86_64-2010-07-17\bin> |
| Comments |
| Comment by Michael Luo [X] [ 10/Jun/14 ] |
|
i'm seeing this error on 2.6.1 on Windows 2008R2. |
| Comment by Jason R. Coombs [ 24/May/13 ] |
|
I'm seeing this error on 2.4.3 on Windows 8 64-bit. |
| Comment by Tad Marshall [ 28/Aug/12 ] |
|
It's not exactly "still outstanding" because it was working fine in 2.1.0; later changes broke it again. But yes, you get this error message in the current code. The explanation is that mongod.exe is exiting from a callback thread created by the Windows Service Control Manager when it calls us due to "net stop mongodb" and this breaks the RPC pipe it used to create the callback thread. We need to reorganize our exit logic to avoid doing this. The error message is the only real effect of this issue; we exit on command, cleanly, and inform the Windows Service Control Manager that we are stopped, but then the "net" command displays an error message because we didn't return from the RPC call they way it expected us to. |
| Comment by John A [ 28/Aug/12 ] |
|
This looks to still be outstanding as of v2.2.0 RC3 https://jira.mongodb.org/browse/SERVER-6771 |
| Comment by Zeng Jie [ 16/Jan/12 ] |
|
This bug has been fixed as |
| Comment by Zeng Jie [ 16/Jan/12 ] |
|
MongoDB 1.8.0 and 1.9.0 also have this problem. It seems that the two github commits above failed to fix the bug. |
| Comment by Zeng Jie [ 16/Jan/12 ] |
|
I can reproduce this bug easily with MongoDB 2.0.2 on Windows 7 64bit or Windows 2008 R2 64bit. Log file: |
| Comment by auto [ 16/Mar/11 ] |
|
Author: {u'login': u'rstam', u'name': u'rstam', u'email': u'robert@10gen.com'}Message: Fixed |
| Comment by auto [ 15/Mar/11 ] |
|
Author: {u'login': u'rstam', u'name': u'rstam', u'email': u'robert@10gen.com'}Message: Fixed |
| Comment by Brian Clark [ 07/Feb/11 ] |
|
I can confirm that this same error exists on Windows 2008 R2 64-bit edition. |
| Comment by Justin Dearing [ 25/Sep/10 ] |
|
Still busted: C:\src\mongo>net start mongodb The Mongo DB service was started successfully. C:\src\mongo>net stop mongodb The pipe has been ended. C:\src\mongo>'
C:\src\mongo>type c:\data\logs\mongo.log reslen:398 629ms Sat Sep 25 09:00:17 dbexit: really exiting now C:\src\mongo> |
| Comment by Eliot Horowitz (Inactive) [ 25/Sep/10 ] |
|
Can you try this on master? |
| Comment by Justin Dearing [ 04/Sep/10 ] |
|
http://github.com/zippy1981/mongo/commit/e01584f27e6de929777a859db637c41b2782bfa1 That seems to fix this 109 error, but not the errors in the log. |