[SERVER-12003] MongoDB server crushes when db.$cmd.sys.inprog is accessed from shell Created: 07/Dec/13  Updated: 10/Dec/14  Resolved: 07/Dec/13

Status: Closed
Project: Core Server
Component/s: Admin, Internal Code, Querying, Shell, Stability
Affects Version/s: 2.4.8
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Ron Warshawsky Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Oracle EE Linux x64

Linux oraclelinux6.localdomain 2.6.39-400.17.1.el6uek.x86_64 #1 SMP Fri Feb 22 18:16:18 PST 2013 x86_64 x86_64 x86_64 GNU/Linux


Issue Links:
Duplicate
duplicates SERVER-10538 Passing $where predicate to db.curren... Closed
Operating System: ALL
Participants:

 Description   

1. start mongo shell
2. use admin
3. authenticate
4. Issue:
db.$cmd.sys.inprog.findOne("$all")

Shell output:

> db.$cmd.sys.inprog.findOne("$all")
Fri Dec 6 20:34:56.719 DBClientCursor::init call() failed
Fri Dec 6 20:34:56.722 Error: error doing query: failed at src/mongo/shell/query.js:78
Fri Dec 6 20:34:56.732 trying reconnect to 127.0.0.1:27017
Fri Dec 6 20:34:56.736 reconnect 127.0.0.1:27017 failed couldn't connect to server 127.0.0.1:27017

MongoDB server log:

Fri Dec 6 20:32:45.661 Invalid access at address: 0x20 from thread: conn35

Fri Dec 6 20:32:45.676 Got signal: 11 (Segmentation fault).

Fri Dec 6 20:32:45.867 Backtrace:
0xde05e1 0x6d0559 0x6d0ae2 0x323b40f500 0xa3f5c4 0xa439b3 0xa442b5 0x9f9628 0x9fbe11 0x6e83a8 0xdccbae 0x323b407851 0x323ace894d
/usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0xde05e1]
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x6d0559]
/usr/bin/mongod(_ZN5mongo24abruptQuitWithAddrSignalEiP7siginfoPv+0x262) [0x6d0ae2]
/lib64/libpthread.so.0() [0x323b40f500]
/usr/bin/mongod(_ZN5mongo7Matcher10parseWhereERKNS_11BSONElementE+0x84) [0xa3f5c4]
/usr/bin/mongod(_ZN5mongo7Matcher27parseMatchExpressionElementERKNS_11BSONElementEb+0x153) [0xa439b3]
/usr/bin/mongod(_ZN5mongo7MatcherC1ERKNS_7BSONObjEb+0x1a5) [0xa442b5]
/usr/bin/mongod(_ZN5mongo9inProgCmdERNS_7MessageERNS_10DbResponseE+0x638) [0x9f9628]
/usr/bin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0x7e1) [0x9fbe11]
/usr/bin/mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x98) [0x6e83a8]
/usr/bin/mongod(_ZN5mongo17PortMessageServer17handleIncomingMsgEPv+0x42e) [0xdccbae]
/lib64/libpthread.so.0() [0x323b407851]
/lib64/libc.so.6(clone+0x6d) [0x323ace894d]



 Comments   
Comment by J Rassi [ 07/Dec/13 ]

This is a known issue affecting versions 2.2 and 2.4 of the server – see the original report at SERVER-10538. Resolving this ticket as a dup.

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