[SERVER-4655] Segmentation fault Created: 10/Jan/12  Updated: 30/Mar/12  Resolved: 10/Jan/12

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

Type: Bug Priority: Major - P3
Reporter: Rosco Assignee: Aaron Staple
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux mongo04 2.6.32-5-amd64 #1 SMP Mon Oct 3 03:59:20 UTC 2011 x86_64 GNU/Linux


Issue Links:
Duplicate
duplicates SERVER-3961 Segmentation Fault when creating new ... Closed
Operating System: Linux
Participants:

 Description   

Tue Jan 10 11:27:27 [conn2510] CMD: drop catalog_ru_front.catalog
Tue Jan 10 11:27:28 [conn2510] command catalog_ru_front.$cmd command:

{ drop: "catalog" }

ntoreturn:1 reslen:131 1123ms
Tue Jan 10 11:27:28 [conn2510] end connection 10.20.30.12:40117
Tue Jan 10 11:27:28 [initandlisten] connection accepted from 10.20.30.12:40127 #2511
Tue Jan 10 11:27:28 Invalid access at address: 0

Tue Jan 10 11:27:28 Got signal: 11 (Segmentation fault).

Tue Jan 10 11:27:29 Backtrace:
0x581483 0x89bedc 0x89c2c2 0x7f5683843f60 0x565971 0x75e1a3 0x75e296 0x75e37c 0x7f5152 0x7aa24e 0x7b1633 0x7b1a4d 0x7b3791 0x7b3fa1 0x7b4878 0x7ed9de 0x7855ae 0x8a2768 0x5e3322 0x7f568383b8ba
/usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x23) [0x581483]
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x34c) [0x89bedc]
/usr/bin/mongod(_ZN5mongo24abruptQuitWithAddrSignalEiP7siginfoPv+0x1d2) [0x89c2c2]
/lib/libpthread.so.0(+0xef60) [0x7f5683843f60]
/usr/bin/mongod(_ZN5mongo24FieldRangeVectorIterator7advanceERKNS_7BSONObjE+0x41) [0x565971]
/usr/bin/mongod(_ZN5mongo11BtreeCursor29skipOutOfRangeKeysAndCheckEndEv+0x63) [0x75e1a3]
/usr/bin/mongod(_ZN5mongo11BtreeCursor12skipAndCheckEv+0x26) [0x75e296]
/usr/bin/mongod(_ZN5mongo11BtreeCursor7advanceEv+0x8c) [0x75e37c]
/usr/bin/mongod(_ZN5mongo11UserQueryOp4nextEv+0x222) [0x7f5152]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet6Runner6nextOpERNS_7QueryOpE+0x1e) [0x7aa24e]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet6Runner4nextEv+0x43) [0x7b1633]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet6Runner22runUntilFirstCompletesEv+0x6d) [0x7b1a4d]
/usr/bin/mongod(_ZN5mongo12QueryPlanSet5runOpERNS_7QueryOpE+0x41) [0x7b3791]
/usr/bin/mongod(_ZN5mongo16MultiPlanScanner9runOpOnceERNS_7QueryOpE+0x3f1) [0x7b3fa1]
/usr/bin/mongod(_ZN5mongo16MultiPlanScanner5runOpERNS_7QueryOpE+0x18) [0x7b4878]
/usr/bin/mongod(ZN5mongo8runQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1+0x9ae) [0x7ed9de]
/usr/bin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0xd8e) [0x7855ae]
/usr/bin/mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x88) [0x8a2768]
/usr/bin/mongod(_ZN5mongo3pms9threadRunEPNS_13MessagingPortE+0x262) [0x5e3322]
/lib/libpthread.so.0(+0x68ba) [0x7f568383b8ba]

Tue Jan 10 11:27:29 dbexit:
Tue Jan 10 11:27:29 [conn2508] shutdown: going to close listening sockets...
Tue Jan 10 11:27:29 [conn2508] closing listening socket: 5
Tue Jan 10 11:27:29 [conn2508] closing listening socket: 6
Tue Jan 10 11:27:29 [conn2508] closing listening socket: 7
Tue Jan 10 11:27:29 [conn2508] removing socket file: /tmp/mongodb-27017.sock
Tue Jan 10 11:27:29 [conn2508] shutdown: going to flush diaglog...
Tue Jan 10 11:27:29 [conn2508] shutdown: going to close sockets...
Tue Jan 10 11:27:29 [conn2508] shutdown: waiting for fs preallocator...
Tue Jan 10 11:27:29 [conn2508] shutdown: closing all files...
Tue Jan 10 11:27:29 [conn2508] closeAllFiles() finished
Tue Jan 10 11:27:29 [conn2508] shutdown: removing fs lock...
Tue Jan 10 11:27:29 dbexit: really exiting now
Logstream::get called in uninitialized state
Tue Jan 10 11:27:29 [conn2508] ERROR: Client::~Client _context should be null but is not; client:conn



 Comments   
Comment by Aaron Staple [ 10/Jan/12 ]

Hi Rosco - this is likely due to SERVER-3961, which was fixed in 2.0.1. If you provide the mongod log I can try to confirm the cause. I'd recommend upgrading to 2.0.2. Please feel free to reopen the ticket if you need additional assistance.

Comment by Rosco [ 10/Jan/12 ]

Sorry, I have mistaken. Correct affected version to 2.0.0. Thank you.

Comment by Aaron Staple [ 10/Jan/12 ]

Hi Rosco - can you provide the full mongod log? Also, can you double check your mongo version - is it 2.0.1?

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