Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-15053

MongoDB throws segmentation fault while running aggregation

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 2.6.4
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      Ubuntu 12.04
    • Operating System:
      Linux

      Description

      2014-08-27T15:34:26.007+0000 [conn5314] SEVERE: Invalid access at address: 0xece2ac08
      2014-08-27T15:34:26.027+0000 [conn5314] SEVERE: Got signal: 11 (Segmentation fault).
      Backtrace:0x11e6111 0x11e54ee 0x11e55df 0x7f151ebfbcb0 0xaac37f 0xd5570c 0xd5622d 0xd5932e 0xc6e7c4 0xc6eec5 0xc7e9b3 0xc80046 0xca0a0f 0xca0e29 0xcfc7bb 0x9b3816 0xa2889a 0xa29ce2 0xa2bea6 0xd5dd6d
      /usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0x11e6111]
      /usr/bin/mongod() [0x11e54ee]
      /usr/bin/mongod() [0x11e55df]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0) [0x7f151ebfbcb0]
      /usr/bin/mongod(_ZN5mongo18KeepMutationsStage4workEPm+0xef) [0xaac37f]
      /usr/bin/mongod(_ZN5mongo15MultiPlanRunner12workAllPlansEPNS_7BSONObjEm+0x13c) [0xd5570c]
      /usr/bin/mongod(_ZN5mongo15MultiPlanRunner12pickBestPlanEPmPNS_7BSONObjE+0xed) [0xd5622d]
      /usr/bin/mongod(_ZN5mongo15MultiPlanRunner7getNextEPNS_7BSONObjEPNS_7DiskLocE+0x34e) [0xd5932e]
      /usr/bin/mongod(_ZN5mongo20DocumentSourceCursor9loadBatchEv+0x1e4) [0xc6e7c4]
      /usr/bin/mongod(_ZN5mongo20DocumentSourceCursor7getNextEv+0x115) [0xc6eec5]
      /usr/bin/mongod(_ZN5mongo19DocumentSourceGroup8populateEv+0x73) [0xc7e9b3]
      /usr/bin/mongod(_ZN5mongo19DocumentSourceGroup7getNextEv+0x426) [0xc80046]
      /usr/bin/mongod(_ZN5mongo18DocumentSourceSort8populateEv+0x12f) [0xca0a0f]
      /usr/bin/mongod(_ZN5mongo18DocumentSourceSort7getNextEv+0xb9) [0xca0e29]
      /usr/bin/mongod(_ZN5mongo8Pipeline3runERNS_14BSONObjBuilderE+0x8b) [0xcfc7bb]
      /usr/bin/mongod(_ZN5mongo15PipelineCommand3runERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb+0x526) [0x9b3816]
      /usr/bin/mongod(_ZN5mongo12_execCommandEPNS_7CommandERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb+0x3a) [0xa2889a]
      /usr/bin/mongod(_ZN5mongo7Command11execCommandEPS0_RNS_6ClientEiPKcRNS_7BSONObjERNS_14BSONObjBuilderEb+0x1042) [0xa29ce2]
      /usr/bin/mongod(_ZN5mongo12_runCommandsEPKcRNS_7BSONObjERNS_11_BufBuilderINS_16TrivialAllocatorEEERNS_14BSONObjBuilderEbi+0x6c6) [0xa2bea6]
      /usr/bin/mongod(_ZN5mongo11newRunQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_+0x22ed) [0xd5dd6d]

      I previously posted SERVER-14969, which was similar, but I don't think it's related since there are no index jobs or drops running in the background at this point.
      I disabled some of the logging feature at the machine while this occurred, so unfortunately I don't have any additional logs I can provide or the type of query/command that ran in order to cause the segmentation fault.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: