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

Mongod dies on start with Fatal assertion 28579 NoSuchKey

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.0
    • Component/s: Storage, WiredTiger
    • None
    • ALL
    • Hide

      1. Run out of log space
      2. Reboot

      Show
      1. Run out of log space 2. Reboot
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Hey!

      I am using Mongo DB 3.2. I have a non sharded environment. My OS is Ubuntu 14.04.

      The instance ran out of log space, and thus it experienced an unclean shutdown. I followed through the standard lock removal and repair steps, but I keep getting this:

      [initandlisten] Fatal assertion 28579 NoSuchKey Unable to find metadata for table:

      My bug is essentially the one described here: https://jira.mongodb.org/browse/SERVER-19274

      It says it was fixed in 3.2.0 but I am getting it now.

      Any tips on how to fix this?

            Assignee:
            kelsey.schubert@mongodb.com Kelsey Schubert
            Reporter:
            michael_xyz Michael
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: