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

MongoDB Error: Unable to read storage Engine Meta Data

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: WiredTiger
    • Environment:
      RHEL 7.3
    • ALL

      Mongodb is getting down while in the midnight may be due to load. But how to avoid this

      Todays error :

      Unable to read the storage engine metadata file: FileNotOpen: Failed to read metadata from /var/lib/mongo/storage.bson
      2017-08-10T03:00:47.483+0100 I - [initandlisten] Fatal Assertion 28661
      2017-08-10T03:00:47.483+0100 I - [initandlisten]

      ***aborting after fassert() failure

      2017-08-10T03:00:47.501+0100 F - [initandlisten] Got signal: 6 (Aborted).

      YEsterday :

      2017-08-09T03:00:42.850+0100 E STORAGE [initandlisten] Unable to read the storage engine metadata file: FileNotOpen: Failed to read metadata from /var/lib/mongo/storage.bson
      2017-08-09T03:00:42.850+0100 I - [initandlisten] Fatal Assertion 28661
      2017-08-09T03:00:42.850+0100 I - [initandlisten]

      ***aborting after fassert() failure

      2017-08-09T03:00:42.858+0100 F - [initandlisten] Got signal: 6 (Aborted).

            Assignee:
            kelsey.schubert@mongodb.com Kelsey Schubert
            Reporter:
            gg.anands@gmail.com Anand Mohan
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: