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

Mongodb seg fault after network interface reset

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • ALL

    Description

      Since we are using Azure as a cloud provider for the VMs, we have a mongodb instance that after some changes in the network (out of our control) caused to segfault.

       

       

      Attachments

        1. 20190605_02_mongodump.log
          78 kB
        2. 20190605_03_mongodump.log
          1.09 MB
        3. 20190605_mongodump.log
          72 kB
        4. 20190608_outlog_mongodb_crash.log
          562 kB
        5. db.out
          10 kB
        6. mongo_dead.log
          106 kB
        7. mongo_sharding_error.log
          15 kB
        8. syslog.out
          4 kB

        Activity

          People

            brian.lane@mongodb.com Brian Lane
            djo Dame Jovanoski
            Votes:
            1 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: