[SERVER-658] Ctrl-C signal Assertion failure c db\client.cpp 161 Created: 23/Feb/10  Updated: 12/Jul/16  Resolved: 24/Feb/10

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: michael haraburda Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows XP 32-bit (SP3)


Participants:

 Description   

Ctrl-C doesn't close gracefully with the lastest nightly build (Feb 23rd 2010)

mongodb-bleeding\bin>mongod --config m.cfg
Tue Feb 23 13:40:23 Mongo DB : starting : pid = 0 port = 27333 dbpath = c:/mh/mongodb-data/dev master = 0 slave = 0 32-bit

Tue Feb 23 13:40:24 db version v1.3.3-, pdfile version 4.5
Tue Feb 23 13:40:24 git version: 6370984c5dd2d3982cb0c3b99cedbe99a41cd301
Tue Feb 23 13:40:24 sys info: windows (5, 1, 2600, 2, 'Service Pack 3') BOOST_LIB_VERSION=1_35
Tue Feb 23 13:40:24 waiting for connections on port 27333
Tue Feb 23 13:40:24 web admin interface listening on port 28333
<snip>
Tue Feb 23 13:42:34 Ctrl-C signal
Tue Feb 23 13:42:34 got kill or ctrl c signal, will terminate after current cmd
ends
Tue Feb 23 13:42:34 Assertion failure c db\client.cpp 161

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

I was previously using the nightly build from 1-28-2010 where it closed as expected



 Comments   
Comment by Eliot Horowitz (Inactive) [ 24/Feb/10 ]

no problem

Comment by michael haraburda [ 24/Feb/10 ]

How embarassing, That error is the build from 2/12 (I believe), not yesterday's

Sorry.

The 2/24 nightly closes correctly:

\mongodb-bleeding\bin>mongod --config m.cfg
Wed Feb 24 15:40:46 Mongo DB : starting : pid = 0 port = 27333 dbpath = c:/mh/mongodb-data/dev master = 0 slave = 0 32-bit

Wed Feb 24 15:40:46 db version v1.3.3-, pdfile version 4.5
Wed Feb 24 15:40:46 git version: c0e6f059435869604765b4059e6188c9e5b2a357
Wed Feb 24 15:40:46 sys info: windows (5, 1, 2600, 2, 'Service Pack 3') BOOST_LIB_VERSION=1_35
Wed Feb 24 15:40:46 waiting for connections on port 27333
Wed Feb 24 15:40:46 web admin interface listening on port 28333
Wed Feb 24 15:43:11 Ctrl-C signal
Wed Feb 24 15:43:11 got kill or ctrl-c signal, will terminate after current cmd ends
Wed Feb 24 15:43:11 now exiting
Wed Feb 24 15:43:11 dbexit:
Wed Feb 24 15:43:11 shutdown: going to close listening sockets...
Wed Feb 24 15:43:11 going to close listening socket: 1856
Wed Feb 24 15:43:11 going to close listening socket: 1884
Wed Feb 24 15:43:11 shutdown: going to flush oplog...
Wed Feb 24 15:43:11 shutdown: going to close sockets...
Wed Feb 24 15:43:11 shutdown: waiting for fs preallocator...
Wed Feb 24 15:43:11 shutdown: closing all files...
Wed Feb 24 15:43:11 Wed Feb 24 15:43:11 MiniWebServer: accept() returns -1 errno:0 No error
closeAllFiles() finished
Wed Feb 24 15:43:11 dbexit: really exiting now

Comment by Eliot Horowitz (Inactive) [ 24/Feb/10 ]

there should be a different header maybe
can you and copy and paste the entire session again

Comment by michael haraburda [ 24/Feb/10 ]

Whoops, I extracted an old version, let me try this again.

Comment by Eliot Horowitz (Inactive) [ 23/Feb/10 ]

added debugging - can you re-test tomorrow 2/24

Generated at Thu Feb 08 02:54:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.