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

MongoDB crash on addition to a replica set

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.4.8
    • Component/s: Replication
    • Labels:
      None
    • ALL

      I added a new server to an existing replica set and the mongod instance on the new replica set hit the following assert and stopped. I am provide the full log if needed. The version is 2.4.8

      Wed May 7 02:08:56.572 [conn74760] authenticate db: data

      { authenticate: 1, user: "admin", nonce: "b72c73378e4a2ed4", key: "ab9cb1fa033cbe6cee07d97661ac6507" }

      Wed May 7 02:08:56.572 [conn74767] end connection 162.243.83.99:42063 (276 connections now open)
      /usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x26) [0xc18f56]
      /usr/bin/mongod(_ZN5mongo13fassertFailedEi+0x63) [0xbdfda3]
      /usr/bin/mongod(_ZN5mongo7replset21multiInitialSyncApplyERKSt6vectorINS_7BSONObjESaIS2_EEPNS0_8SyncTailE+0x164) [0xad9824]
      /usr/bin/mongod(_ZN5mongo10threadpool6Worker4loopEv+0x41c) [0xbec29c]
      /usr/bin/mongod() [0xc5257c]
      /lib64/libpthread.so.0(+0x7851) [0x7f1f33a86851]
      /lib64/libc.so.6(clone+0x6d) [0x7f1f327e090d]
      Wed May 7 02:08:56.572 [conn74768] end connection 162.243.122.196:59338 (276 connections now open)
      Wed May 7 02:08:56.583 [repl writer worker 1]

      ***aborting after fassert() failure

        1. mongod.log
          32.75 MB

            Assignee:
            matt.dannenberg Matt Dannenberg
            Reporter:
            dharshanr@scalegrid.net Dharshan Rangegowda
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: