-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
I am running MongoDB v3.2.16 from official docker image.
I can't start mongo after space on the server was the end. Now I added few GB, but the MongoDB can't start.
2017-09-18T08:16:03.311+0000 I CONTROL [initandlisten] db version v3.2.16
2017-09-18T08:16:03.311+0000 I CONTROL [initandlisten] git version: 056bf45128114e44c5358c7a8776fb582363e094
2017-09-18T08:16:03.311+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1t 3 May 2016
2017-09-18T08:16:03.311+0000 I CONTROL [initandlisten] allocator: tcmalloc
2017-09-18T08:16:03.311+0000 I CONTROL [initandlisten] modules: none
2017-09-18T08:16:03.311+0000 I CONTROL [initandlisten] build environment:
2017-09-18T08:16:03.311+0000 I CONTROL [initandlisten] distmod: debian81
2017-09-18T08:16:03.311+0000 I CONTROL [initandlisten] distarch: x86_64
2017-09-18T08:16:03.311+0000 I CONTROL [initandlisten] target_arch: x86_64
2017-09-18T08:16:03.311+0000 I CONTROL [initandlisten] options: { storage: { journal:
} }
2017-09-18T08:16:03.315+0000 I - [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2017-09-18T08:16:03.315+0000 I STORAGE [initandlisten] Detected WT journal files. Running recovery from last checkpoint.
2017-09-18T08:16:03.315+0000 I STORAGE [initandlisten] journal to nojournal transition config: create,cache_size=1G,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),
2017-09-18T08:16:03.325+0000 E STORAGE [initandlisten] WiredTiger (-31802) [1505722563:325909][1:0x7f5e4e884cc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
2017-09-18T08:16:03.325+0000 E STORAGE [initandlisten] WiredTiger (0) [1505722563:325939][1:0x7f5e4e884cc0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
2017-09-18T08:16:03.325+0000 E STORAGE [initandlisten] WiredTiger (0) [1505722563:325945][1:0x7f5e4e884cc0], 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-09-18T08:16:03.326+0000 E STORAGE [initandlisten] WiredTiger (0) [1505722563:325985][1:0x7f5e4e884cc0], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
2017-09-18T08:16:03.326+0000 I - [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error
2017-09-18T08:16:03.326+0000 I STORAGE [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2017-09-18T08:16:03.326+0000 I CONTROL [initandlisten] dbexit: rc: 100
- is duplicated by
-
SERVER-31125 file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt
-
- Closed
-