Details
-
Bug
-
Resolution: Incomplete
-
Critical - P2
-
None
-
2.0.6
-
$ uname -a
Linux <NODENAME_HIDDEN> #50-Ubuntu SMP Mon Sep 12 21:51:23 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
mongod --version
db version v2.0.6, pdfile version 4.5
Tue Jun 5 23:37:53 git version: e1c0cbc25863f6356aa4e31375add7bb49fb05bc
mongod --version
db version v2.0.6, pdfile version 4.5
Tue Jun 5 23:37:53 git version: e1c0cbc25863f6356aa4e31375add7bb49fb05bc
$ uname -a Linux <NODENAME_HIDDEN> #50-Ubuntu SMP Mon Sep 12 21:51:23 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux mongod --version db version v2.0.6, pdfile version 4.5 Tue Jun 5 23:37:53 git version: e1c0cbc25863f6356aa4e31375add7bb49fb05bc mongod --version db version v2.0.6, pdfile version 4.5 Tue Jun 5 23:37:53 git version: e1c0cbc25863f6356aa4e31375add7bb49fb05bc
-
Linux
Description
Hello. I'm hoping you can help me figure out why my mongod instance crashes when I execute a certain query. When I make the below query, I consistently kill the running mongod instance and receive same error message.
I make the below query to a collection containing 170,941,610 documents. The collection has an index on the field, "transformed".
Tue Jun 5 22:40:25 [conn933] query <DB>.stats_cumulative_stats query:
{ transformed: false }ntoreturn:500000 nscanned:58 255 nreturned:58254 reslen:4194308 607ms
The log shows this error:
Tue Jun 5 22:40:33 Invalid access at address: 0x3d27000
Tue Jun 5 22:40:33 Got signal: 11 (Segmentation fault).
Tue Jun 5 22:40:33 Backtrace:
0xa95ce9 0xa9640c 0x7fbcbcb5dc60 0x7fbcbc0a3885 0x571617 0x911b3f 0x941b2c 0x885a24 0x88e6da 0xaa0bc8 0x6389f7 0x7fbcbcb54d8c 0x7fbcbc0fec2d.
/usr/bin/mongod(_ZN5mongo10abruptQuitEi+0x3a9) [0xa95ce9]
/usr/bin/mongod(_ZN5mongo24abruptQuitWithAddrSignalEiP7siginfoPv+0x22c) [0xa9640c]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfc60) [0x7fbcbcb5dc60]
/lib/x86_64-linux-gnu/libc.so.6(memcpy+0x425) [0x7fbcbc0a3885]
/usr/bin/mongod(_ZNK5mongo10Projection9transformERKNS_7BSONObjERNS_14BSONObjBuilderE+0x147) [0x571617]
/usr/bin/mongod(_ZN5mongo22fillQueryResultFromObjERNS_11_BufBuilderINS_16TrivialAllocatorEEEPNS_10ProjectionERKNS_7BSONObjEPNS_7DiskLocE+0xaf) [0x911b3f]
/usr/bin/mongod(_ZN5mongo14processGetMoreEPKcixRNS_5CurOpEiRb+0x87c) [0x941b2c]
/usr/bin/mongod(_ZN5mongo15receivedGetMoreERNS_10DbResponseERNS_7MessageERNS_5CurOpE+0x1b4) [0x885a24]
/usr/bin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0xf5a) [0x88e6da]
/usr/bin/mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x78) [0xaa0bc8]
/usr/bin/mongod(_ZN5mongo3pms9threadRunEPNS_13MessagingPortE+0x287) [0x6389f7]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6d8c) [0x7fbcbcb54d8c]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7fbcbc0fec2d]
Logstream::get called in uninitialized state
Tue Jun 5 22:40:33 ERROR: Client::~Client _context should be null but is not; client:conn
Logstream::get called in uninitialized state
Tue Jun 5 22:40:33 ERROR: Client::shutdown not called: conn
—
To recover the server, I follow these steps (my db is journaled): First, I start it up with /etc/init.d/mongodb start. At this point, I cannot log in via mongo client (ie mongo --host <HOST>) returns "connect failed". This is the error message:
MongoDB shell version: 2.0.4
connecting to: <HOST>:27017/<DB>
Tue Jun 5 19:03:12 Error: couldn't connect to server <HOST>:<PORT> shell/mongo.js:86
exception: connect failed
Then, I restart server via /etc/init.d/mongodb restart and I can log in as usual via the mongo client.