[SERVER-31125] file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt Created: 18/Sep/17  Updated: 09/Oct/17  Resolved: 18/Sep/17

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Shalva Usubov [X] Assignee: Mark Agarunov
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-31124 WiredTiger (-31802) [1505722563:32590... Closed
Operating System: ALL
Participants:

 Description   

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:44:58.573+0000 I CONTROL [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=5928e5db995f
2017-09-18T08:44:58.573+0000 I CONTROL [initandlisten] db version v3.2.16
2017-09-18T08:44:58.573+0000 I CONTROL [initandlisten] git version: 056bf45128114e44c5358c7a8776fb582363e094
2017-09-18T08:44:58.573+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1t 3 May 2016
2017-09-18T08:44:58.573+0000 I CONTROL [initandlisten] allocator: tcmalloc
2017-09-18T08:44:58.573+0000 I CONTROL [initandlisten] modules: none
2017-09-18T08:44:58.573+0000 I CONTROL [initandlisten] build environment:
2017-09-18T08:44:58.573+0000 I CONTROL [initandlisten] distmod: debian81
2017-09-18T08:44:58.573+0000 I CONTROL [initandlisten] distarch: x86_64
2017-09-18T08:44:58.573+0000 I CONTROL [initandlisten] target_arch: x86_64
2017-09-18T08:44:58.573+0000 I CONTROL [initandlisten] options: {}
2017-09-18T08:44:58.578+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:44:58.578+0000 I STORAGE [initandlisten] wiredtiger_open 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:44:58.589+0000 E STORAGE [initandlisten] WiredTiger (-31802) [1505724298:589859][1:0x7f4248c44cc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
2017-09-18T08:44:58.589+0000 E STORAGE [initandlisten] WiredTiger (0) [1505724298:589924][1:0x7f4248c44cc0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
2017-09-18T08:44:58.589+0000 E STORAGE [initandlisten] WiredTiger (0) [1505724298:589937][1:0x7f4248c44cc0], 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:44:58.589+0000 E STORAGE [initandlisten] WiredTiger (0) [1505724298:589947][1:0x7f4248c44cc0], 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:44:58.590+0000 I - [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error
2017-09-18T08:44:58.590+0000 I STORAGE [initandlisten] exception in initAndListen: 28595 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2017-09-18T08:44:58.590+0000 I CONTROL [initandlisten] dbexit: rc: 100



 Comments   
Comment by Mark Agarunov [ 18/Sep/17 ]

Hello Shalva,

Thank you to the report. As this appears to be the same issue as SERVER-31124, I've closed this ticket as a duplicate. Please watch SERVER-31124 for future updates.

Thanks,
Mark

Generated at Thu Feb 08 04:26:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.