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

3.2.6 Segmentation Fault after a network problem

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • Query 16 (06/24/16), Query 17 (07/15/16), Query 2016-11-21

    Description

      Configuration is a replica set with one primary, one secondary and an arbiter.
      Primary and secondary are running version 3.2.6 on CentOS 6 64-bit.
      Arbiter is running version 2.6.9 on CentOS 6 32-bit.

      After some strange network problem secondary node's mongod process became primary and after cca 5min it crashed with a Segmentation fault.
      I have attached log file, diagnostic.data folder and rs.conf() output.

      Attachments

        1. diagnostic.data.tar.xz
          78.11 MB
        2. mongod.log.xz
          11 kB
        3. rs.conf.txt
          1 kB

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-26868 mongodb 3.2.10 crash (Segmentation fault)

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-27106 Segfaults errors

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-30525 Segmentation Fault

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              charlie.swanson@mongodb.com Charlie Swanson
              sime Šimun Mikecin
              Votes:
              3 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: