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

Unable to start mongo after unclean shutdown

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.4.2
    • Component/s: WiredTiger
    • Labels:
      None
    • ALL

      Greetings,

      I have a mongo instance that had ran out of storage room. Is the error recoverable?

      I have attempted to run mongod with the --repair option, but both yield similar results:

       
      mongod --dbpath /mongodb/data --repair
      2019-04-22T23:05:03.840+1000 I CONTROL  [initandlisten] MongoDB starting : pid=4101 port=27017 dbpath=/mongodb/data 64-bit host=FADAGADB01T.gpaupd.local
      2019-04-22T23:05:03.840+1000 I CONTROL  [initandlisten] db version v3.4.2
      2019-04-22T23:05:03.840+1000 I CONTROL  [initandlisten] git version: 3f76e40c105fc223b3e5aac3e20dcd026b83b38b
      2019-04-22T23:05:03.840+1000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013
      2019-04-22T23:05:03.840+1000 I CONTROL  [initandlisten] allocator: tcmalloc
      2019-04-22T23:05:03.840+1000 I CONTROL  [initandlisten] modules: none
      2019-04-22T23:05:03.840+1000 I CONTROL  [initandlisten] build environment:
      2019-04-22T23:05:03.840+1000 I CONTROL  [initandlisten]     distmod: rhel70
      2019-04-22T23:05:03.840+1000 I CONTROL  [initandlisten]     distarch: x86_64
      2019-04-22T23:05:03.840+1000 I CONTROL  [initandlisten]     target_arch: x86_64
      2019-04-22T23:05:03.840+1000 I CONTROL  [initandlisten] options: { repair: true, storage:

      { dbPath: "/mongodb/data" }

      }
      2019-04-22T23:05:03.865+1000 I -        [initandlisten] Detected data files in /mongodb/data created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
      2019-04-22T23:05:03.865+1000 I STORAGE  [initandlisten] Detected WT journal files.  Running recovery from last checkpoint.
      2019-04-22T23:05:03.865+1000 I STORAGE  [initandlisten] journal to nojournal transition config: create,cache_size=15576M,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
      2019-04-22T23:05:03.877+1000 E STORAGE  [initandlisten] WiredTiger error (0) [1555938303:877190][4101:0x7f9437d11dc0], file:WiredTiger.wt, connection: read checksum error for 4096B block at offset 118784: block header checksum of 2037539182 doesn't match expected checksum of 3071916361
      2019-04-22T23:05:03.877+1000 E STORAGE  [initandlisten] WiredTiger error (0) [1555938303:877238][4101:0x7f9437d11dc0], file:WiredTiger.wt, connection: WiredTiger.wt: encountered an illegal file format or internal value
      2019-04-22T23:05:03.877+1000 E STORAGE  [initandlisten] WiredTiger error (-31804) [1555938303:877254][4101:0x7f9437d11dc0], file:WiredTiger.wt, connection: the process must exit and restart: WT_PANIC: WiredTiger library panic
      2019-04-22T23:05:03.877+1000 I -        [initandlisten] Fatal Assertion 28558 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 361
      2019-04-22T23:05:03.877+1000 I -        [initandlisten]
       
      ***aborting after fassert() failure
       
       
      2019-04-22T23:05:03.896+1000 F -        [initandlisten] Got signal: 6 (Aborted).
       

        1. repair-attempt.tar
          1.99 MB
        2. WiredTiger.turtle
          1.0 kB
        3. WiredTiger.wt
          43.29 MB

            Assignee:
            daniel.hatcher@mongodb.com Danny Hatcher (Inactive)
            Reporter:
            jlangston jeff langston
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: