Mongodb seg fault after network interface reset

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

       

       

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

            Assignee:
            Brian Lane
            Reporter:
            Dame Jovanoski
            Votes:
            1 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: