Details
Description
Mongodb works fine at first.
Then PC reboots without shutting down the mongodb cleanly.
Then we try to start the mongod service again by the same command, it fails and return "dbexit: rc: 100".
Also we're not able to repair the mongodb database.
We're using WiredTiger storage engine.
Attachment is the mongodb log containing the error messages.
2016-06-01T16:55:23.838+0800 I CONTROL [main] ***** SERVER RESTARTED *****
|
2016-06-01T16:55:23.948+0800 I CONTROL [initandlisten] MongoDB starting : pid=2493 port=27017 dbpath=/home/mongodb/data/db 64-bit host=localhost.localdomain
|
2016-06-01T16:55:23.948+0800 I CONTROL [initandlisten] db version v3.2.0
|
2016-06-01T16:55:23.948+0800 I CONTROL [initandlisten] git version: 45d947729a0315accb6d4f15a6b06be6d9c19fe7
|
2016-06-01T16:55:23.948+0800 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013
|
2016-06-01T16:55:23.948+0800 I CONTROL [initandlisten] allocator: tcmalloc
|
2016-06-01T16:55:23.948+0800 I CONTROL [initandlisten] modules: none
|
2016-06-01T16:55:23.948+0800 I CONTROL [initandlisten] build environment:
|
2016-06-01T16:55:23.948+0800 I CONTROL [initandlisten] distmod: rhel70
|
2016-06-01T16:55:23.948+0800 I CONTROL [initandlisten] distarch: x86_64
|
2016-06-01T16:55:23.948+0800 I CONTROL [initandlisten] target_arch: x86_64
|
2016-06-01T16:55:23.948+0800 I CONTROL [initandlisten] options: { net: { port: 27017 }, processManagement: { fork: true }, storage: { dbPath: "/home/mongodb/data/db" }, systemLog: { destination: "file", logAppend: true, path: "/home/mongodb/log/mongodb.log" } }
|
2016-06-01T16:55:24.029+0800 I - [initandlisten] Detected data files in /home/mongodb/data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
|
2016-06-01T16:55:24.029+0800 W - [initandlisten] Detected unclean shutdown - /home/mongodb/data/db/mongod.lock is not empty.
|
2016-06-01T16:55:24.029+0800 W STORAGE [initandlisten] Recovering data from the last clean checkpoint.
|
2016-06-01T16:55:24.029+0800 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=37G,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),
|
2016-06-01T16:55:24.163+0800 E STORAGE [initandlisten] WiredTiger (-31802) [1464771324:163295][2493:0x7f5b28760dc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
|
2016-06-01T16:55:24.163+0800 E STORAGE [initandlisten] WiredTiger (0) [1464771324:163393][2493:0x7f5b28760dc0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
|
2016-06-01T16:55:24.163+0800 E STORAGE [initandlisten] WiredTiger (0) [1464771324:163408][2493:0x7f5b28760dc0], 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
|
2016-06-01T16:55:24.163+0800 E STORAGE [initandlisten] WiredTiger (0) [1464771324:163421][2493:0x7f5b28760dc0], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
|
2016-06-01T16:55:24.164+0800 I - [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error
|
2016-06-01T16:55:24.277+0800 I STORAGE [initandlisten] exception in initAndListen: 28595 -31802: WT_ERROR: non-specific WiredTiger error, terminating
|
2016-06-01T16:55:24.277+0800 I CONTROL [initandlisten] dbexit: rc: 100
|