-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
ALL
Hello Support Team! I need your help.
I am trying to start Mongod on CentOS 7.2 but it looks like Wired Tiger is having troubles reading the data.
Mongo version is: 3.2.4
The full output is:
2022-02-03T17:15:42.137+0800 I CONTROL [initandlisten] MongoDB starting : pid=2913 port=27019 dbpath=/data/test/db 64-bit host=VM_0_13_centos 2022-02-03T17:15:42.137+0800 I CONTROL [initandlisten] db version v3.2.4 2022-02-03T17:15:42.137+0800 I CONTROL [initandlisten] git version: e2ee9ffcf9f5a94fad76802e28cc978718bb7a30 2022-02-03T17:15:42.137+0800 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013 2022-02-03T17:15:42.137+0800 I CONTROL [initandlisten] allocator: tcmalloc 2022-02-03T17:15:42.137+0800 I CONTROL [initandlisten] modules: none 2022-02-03T17:15:42.137+0800 I CONTROL [initandlisten] build environment: 2022-02-03T17:15:42.137+0800 I CONTROL [initandlisten] distmod: rhel70 2022-02-03T17:15:42.137+0800 I CONTROL [initandlisten] distarch: x86_64 2022-02-03T17:15:42.137+0800 I CONTROL [initandlisten] target_arch: x86_64 2022-02-03T17:15:42.137+0800 I CONTROL [initandlisten] options: { config: "mongodb.conf", net: { http: { enabled: false }, port: 27019 }, processManagement: { fork: true }, storage: { dbPath: "/data/test/db" }, systemLog: { destination: "file", path: "/data/test/logs/mongodb.log" } } 2022-02-03T17:15:42.148+0800 I - [initandlisten] Detected data files in /data/test/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. 2022-02-03T17:15:42.148+0800 W - [initandlisten] Detected unclean shutdown - /data/test/db/mongod.lock is not empty. 2022-02-03T17:15:42.148+0800 W STORAGE [initandlisten] Recovering data from the last clean checkpoint. 2022-02-03T17:15:42.148+0800 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), 2022-02-03T17:15:42.155+0800 E STORAGE [initandlisten] WiredTiger (-31802) [1643879742:155879][2913:0x7fae94e5be00], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error 2022-02-03T17:15:42.155+0800 E STORAGE [initandlisten] WiredTiger (0) [1643879742:155927][2913:0x7fae94e5be00], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata 2022-02-03T17:15:42.155+0800 E STORAGE [initandlisten] WiredTiger (0) [1643879742:155934][2913:0x7fae94e5be00], 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 2022-02-03T17:15:42.155+0800 E STORAGE [initandlisten] WiredTiger (0) [1643879742:155944][2913:0x7fae94e5be00], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options 2022-02-03T17:15:42.156+0800 I - [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error 2022-02-03T17:15:42.156+0800 I STORAGE [initandlisten] exception in initAndListen: 28595 -31802: WT_ERROR: non-specific WiredTiger error, terminating 2022-02-03T17:15:42.156+0800 I CONTROL [initandlisten] dbexit: rc: 100
I am sending the two files usually attached to similar tickets I've found online.Thanks a lot for your help,