Fatal Assertion 16137

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.6.5
    • Component/s: Concurrency
    • None
    • ALL
    • Quint Iteration 4, Quint Iteration 5
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Hello,

      we run a single mongod instance on Ubuntu 14.10 server. The version of db is
      —
      db version v2.6.5
      git version: e99d4fcb4279c0279796f237aa92fe3b64560bf6
      build info: Linux build8.nj1.10gen.cc 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49
      —

      Today mongod crashed with the following error:

      2015-01-23T19:29:41.183+0100 [conn219322] Fatal Assertion 16137
2015-01-23T19:29:41.196+0100 [conn219322] 0x11e9b11 0x118b849 0x116e37d 0xa1d354 0xa1e084 0xd5f0b9 0xba1052 0xba2630 0x770d5f 0x119f93e 0x7f4167bd10a5 0x7f4166eca84d
 /usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0x11e9b11]
 /usr/bin/mongod(_ZN5mongo10logContextEPKc+0x159) [0x118b849]
 /usr/bin/mongod(_ZN5mongo13fassertFailedEi+0xcd) [0x116e37d]
 /usr/bin/mongod(_ZN5mongo4Lock6DBRead8unlockDBEv+0x1a4) [0xa1d354]
 /usr/bin/mongod(_ZN5mongo4Lock6DBReadD0Ev+0x24) [0xa1e084]
 /usr/bin/mongod(_ZN5mongo11newRunQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_+0x1b89) [0xd5f0b9]
 /usr/bin/mongod() [0xba1052]
 /usr/bin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0x580) [0xba2630]
 /usr/bin/mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x9f) [0x770d5f]
 /usr/bin/mongod(_ZN5mongo17PortMessageServer17handleIncomingMsgEPv+0x4ee) [0x119f93e]
 /lib/x86_64-linux-gnu/libpthread.so.0(+0x80a5) [0x7f4167bd10a5]
 /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f4166eca84d]
2015-01-23T19:29:41.197+0100 [conn219322]

***aborting after fassert() failure


2015-01-23T19:29:41.200+0100 [conn219322] SEVERE: Got signal: 6 (Aborted).
Backtrace:0x11e9b11 0x11e8eee 0x7f4166e06da0 0x7f4166e06d27 0x7f4166e08418 0x116e3ea 0xa1d354 0xa1e084 0xd5f0b9 0xba1052 0xba2630 0x770d5f 0x119f93e 0x7f4167bd10a5 0x7f4166eca84d
 /usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0x11e9b11]
 /usr/bin/mongod() [0x11e8eee]
 /lib/x86_64-linux-gnu/libc.so.6(+0x36da0) [0x7f4166e06da0]
 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f4166e06d27]
 /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f4166e08418]
 /usr/bin/mongod(_ZN5mongo13fassertFailedEi+0x13a) [0x116e3ea]
 /usr/bin/mongod(_ZN5mongo4Lock6DBRead8unlockDBEv+0x1a4) [0xa1d354]
 /usr/bin/mongod(_ZN5mongo4Lock6DBReadD0Ev+0x24) [0xa1e084]
 /usr/bin/mongod(_ZN5mongo11newRunQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_+0x1b89) [0xd5f0b9]
 /usr/bin/mongod() [0xba1052]
 /usr/bin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0x580) [0xba2630]
 /usr/bin/mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x9f) [0x770d5f]
 /usr/bin/mongod(_ZN5mongo17PortMessageServer17handleIncomingMsgEPv+0x4ee) [0x119f93e]
 /lib/x86_64-linux-gnu/libpthread.so.0(+0x80a5) [0x7f4167bd10a5]
 /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f4166eca84d]

      Previous message in logs with this conn219322 is about 13 min before:

      2015-01-23T19:16:58.394+0100 [conn219322] command probtn.$cmd command: findAndModify { findandmodify: "UserStatistic", query: { _id: ObjectId('54a042b94e27d95663057f32') }, sort: { _id: 1 }, new: 0, remove: 0, upsert: 0, update: { $set: { ...  } } } keyUpdates:0 numYields:0 locks(micros) w:130567 reslen:373 130ms

      (note that I removed data from $set for privacy reasons).
      After restart mongod didn't crash again.

      We communicate with db from our application via http://mongodb.github.io/node-mongodb-native/ driver version 1.3.15

            Assignee:
            David Storch
            Reporter:
            quantomass
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: