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

WiredTiger error (-31802)

XMLWordPrintableJSON

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

      I only backup my whole mongo directory without stopping the mongod instance, after finishing the System initialization, I returned mongo directory and try "bin/mongod -f mongo.conf", it fails. Then I check the mongo.log and find out that these must be some corruption happened. I tried "repair" and it fails with the log bellow. I also tried WiredTiger tools and it fails with almost same err. please help me. Dataset here is very important for me .

      2019-05-26T12:23:10.481+0800 I CONTROL  [main] ** WARNING: --rest is specified without --httpinterface,
2019-05-26T12:23:10.481+0800 I CONTROL  [main] **          enabling http interface
[root@iZbp13lmtcdw0hu47yyxmhZ mongodb]# vim mongo.log2019-05-26T12:23:10.507+0800 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
2019-05-26T12:23:10.507+0800 I STORAGE  [initandlisten] Detected WT journal files.  Running recovery from last checkpoint.
2019-05-26T12:23:10.507+0800 I STORAGE  [initandlisten] journal to nojournal transition config: create,cache_size=1468M,session_max=20000,eviction=(threads_min=4,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-05-26T12:23:10.561+0800 E STORAGE  [initandlisten] WiredTiger error (-31802) [1558844590:561589][9740:0x7f1a255a3ce0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
2019-05-26T12:23:10.561+0800 E STORAGE  [initandlisten] WiredTiger error (0) [1558844590:561652][9740:0x7f1a255a3ce0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
2019-05-26T12:23:10.561+0800 E STORAGE  [initandlisten] WiredTiger error (0) [1558844590:561663][9740:0x7f1a255a3ce0], file:WiredTiger.wt, connection: This may be due to the database files being encrypted, being from an older version or due to corruption on disk
2019-05-26T12:23:10.561+0800 E STORAGE  [initandlisten] WiredTiger error (0) [1558844590:561673][9740:0x7f1a255a3ce0], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
2019-05-26T12:23:10.562+0800 I -        [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 253
2019-05-26T12:23:10.562+0800 I STORAGE  [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2019-05-26T12:23:10.562+0800 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
2019-05-26T12:23:10.562+0800 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-27017.sock
2019-05-26T12:23:10.562+0800 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
2019-05-26T12:23:10.562+0800 I CONTROL  [initandlisten] now exiting
2019-05-26T12:23:10.562+0800 I CONTROL  [initandlisten] shutting down with code:100

        1. _mdb_catalog.wt
          80 kB
        2. mongo.conf
          0.2 kB
        3. SERVER-41323_repair_attempt.tgz
          75 kB
        4. WiredTiger
          0.0 kB
        5. WiredTiger.lock
          0.0 kB
        6. WiredTiger.turtle
          1.0 kB
        7. WiredTiger.wt
          1.29 MB
        8. WiredTigerLAS.wt
          4 kB

            Assignee:
            eric.sedor@mongodb.com Eric Sedor
            Reporter:
            zhuangdanyang zhuangdanyang
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: