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

file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.5
    • Component/s: WiredTiger
    • Linux

      I am running mongodb 3.2.5 in Cent OS 6.4.

      After a unclean down the server.I start mongod server use following command ,but i got failed

      please kindly help me.

      /home/xiangdong/soft/mongodb/bin/mongod --port 53100 --dbpath /home/xiangdong/mongo/63100/ --storageEngine wiredTiger --wiredTigerCacheSizeGB 1

      2017-01-22T08:41:53.602-0400 I CONTROL [initandlisten] MongoDB starting : pid=4827 port=53100 dbpath=/home/xiangdong/mongo/63100/ 64-bit host=localhost.localdomain
      2017-01-22T08:41:53.603-0400 I CONTROL [initandlisten] db version v3.2.5
      2017-01-22T08:41:53.603-0400 I CONTROL [initandlisten] git version: 34e65e5383f7ea1726332cb175b73077ec4a1b02
      2017-01-22T08:41:53.603-0400 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013
      2017-01-22T08:41:53.603-0400 I CONTROL [initandlisten] allocator: tcmalloc
      2017-01-22T08:41:53.603-0400 I CONTROL [initandlisten] modules: none
      2017-01-22T08:41:53.603-0400 I CONTROL [initandlisten] build environment:
      2017-01-22T08:41:53.603-0400 I CONTROL [initandlisten] distmod: rhel62
      2017-01-22T08:41:53.603-0400 I CONTROL [initandlisten] distarch: x86_64
      2017-01-22T08:41:53.603-0400 I CONTROL [initandlisten] target_arch: x86_64
      2017-01-22T08:41:53.603-0400 I CONTROL [initandlisten] options: { net:

      { port: 53100 }

      , storage: { dbPath: "/home/xiangdong/mongo/63100/", engine: "wiredTiger", wiredTiger: { engineConfig:

      { cacheSizeGB: 1 }

      } } }
      2017-01-22T08:41:53.656-0400 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=1G,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),
      2017-01-22T08:41:53.669-0400 E STORAGE [initandlisten] WiredTiger (-31802) [1485088913:669470][4827:0x7f6d66d3cd40], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
      2017-01-22T08:41:53.669-0400 E STORAGE [initandlisten] WiredTiger (0) [1485088913:669535][4827:0x7f6d66d3cd40], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
      2017-01-22T08:41:53.669-0400 E STORAGE [initandlisten] WiredTiger (0) [1485088913:669563][4827:0x7f6d66d3cd40], 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
      2017-01-22T08:41:53.669-0400 E STORAGE [initandlisten] WiredTiger (0) [1485088913:669588][4827:0x7f6d66d3cd40], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
      2017-01-22T08:41:53.670-0400 I - [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error
      2017-01-22T08:41:53.671-0400 I STORAGE [initandlisten] exception in initAndListen: 28595 -31802: WT_ERROR: non-specific WiredTiger error, terminating
      2017-01-22T08:41:53.671-0400 I CONTROL [initandlisten] dbexit: rc: 100

        1. repair_attempt.tar.gz
          83 kB
          Kelsey Schubert
        2. repair_attempt-2.tar.gz
          80 kB
          Kelsey Schubert
        3. WiredTiger.turtle
          0.9 kB
          frankzou
        4. WiredTiger.wt
          1.68 MB
          frankzou
        5. wt-bak.rar
          42 kB
          frankzou

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

              Created:
              Updated:
              Resolved: