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

Invalid access at address: <hexaddr>; /usr/local/mongo/bin/mongod(_ZN5mongo15BSONObjIterator4nextEv+0x27) [0x51a6c7]

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 2.0.6
    • Stability
    • ALL

    Description

      A RS-secondary (member of a 4-shard cluster) segfaulted abruptly during "normal" operation. At the time of the failure, nothing should have been querying the secondary – the live site doesn't do RS reads, and some batch iteration jobs run against the secondaries but at a different time. See first backtrace.

      Removed lockfile and restarted, crashed again. See second backtrace (is removing the lockfile no longer recommended procedure? If so, oops)

      Left lockfile alone and the secondary returned to normal operation.

      Let me know what other information would help. This isn't super high-priority for me since the system returned to normal relatively quickly, but it is somewhat troublesome.

      Attachments

        1. traces.txt
          12 kB
        2. traces-more.txt
          70 kB

        Activity

          People

            matt.dannenberg Matt Dannenberg
            bsg Bobby Joe
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: