[SERVER-38283] file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error Created: 28/Nov/18  Updated: 03/Dec/18  Resolved: 03/Dec/18

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

Type: Bug Priority: Major - P3
Reporter: John Narma Assignee: Danny Hatcher (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File WiredTiger.turtle     File WiredTiger.wt     Text File mongod_--repair_v3.4.txt     Text File mongod_--repair_v3.6.txt     Text File mongod_--repair_v4.0.4.txt    
Operating System: ALL
Participants:

 Description   

Hello.

I met a problem in mongoDB on docker container.

MongoDB can't start with the following error message.

Can I solve this? Thank you.

mongo_1       | 2018-11-28T02:22:31.216+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=1e8d99fdc025
mongo_1       | 2018-11-28T02:22:31.216+0000 I CONTROL  [initandlisten] db version v3.4.8
mongo_1       | 2018-11-28T02:22:31.216+0000 I CONTROL  [initandlisten] git version: 8ef456f89f63ab12941fe6b5352b20cff2522da3
mongo_1       | 2018-11-28T02:22:31.216+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1t  3 May 2016
mongo_1       | 2018-11-28T02:22:31.216+0000 I CONTROL  [initandlisten] allocator: tcmalloc
mongo_1       | 2018-11-28T02:22:31.216+0000 I CONTROL  [initandlisten] modules: none
mongo_1       | 2018-11-28T02:22:31.216+0000 I CONTROL  [initandlisten] build environment:
mongo_1       | 2018-11-28T02:22:31.216+0000 I CONTROL  [initandlisten]     distmod: debian81
mongo_1       | 2018-11-28T02:22:31.216+0000 I CONTROL  [initandlisten]     distarch: x86_64
mongo_1       | 2018-11-28T02:22:31.216+0000 I CONTROL  [initandlisten]     target_arch: x86_64
mongo_1       | 2018-11-28T02:22:31.216+0000 I CONTROL  [initandlisten] options: { storage: { mmapv1: { smallFiles: true } } }
mongo_1       | 2018-11-28T02:22:31.220+0000 I -        [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
mongo_1       | 2018-11-28T02:22:31.220+0000 I STORAGE  [initandlisten]
mongo_1       | 2018-11-28T02:22:31.220+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
mongo_1       | 2018-11-28T02:22:31.220+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
mongo_1       | 2018-11-28T02:22:31.220+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=3479M,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),
mongo_1       | 2018-11-28T02:22:31.233+0000 E STORAGE  [initandlisten] WiredTiger error (-31802) [1543371751:233633][1:0x7f3000274d40], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
mongo_1       | 2018-11-28T02:22:31.233+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1543371751:233718][1:0x7f3000274d40], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
mongo_1       | 2018-11-28T02:22:31.233+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1543371751:233764][1:0x7f3000274d40], 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
mongo_1       | 2018-11-28T02:22:31.233+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1543371751:233793][1:0x7f3000274d40], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
mongo_1       | 2018-11-28T02:22:31.234+0000 I -        [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 269
mongo_1       | 2018-11-28T02:22:31.234+0000 I STORAGE  [initandlisten] exception in initAndListen: 28595 -31802: WT_ERROR: non-specific WiredTiger error, terminating
mongo_1       | 2018-11-28T02:22:31.234+0000 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
mongo_1       | 2018-11-28T02:22:31.234+0000 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-27017.sock
mongo_1       | 2018-11-28T02:22:31.234+0000 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
mongo_1       | 2018-11-28T02:22:31.234+0000 I CONTROL  [initandlisten] now exiting
mongo_1       | 2018-11-28T02:22:31.234+0000 I CONTROL  [initandlisten] shutting down with code:100

WiredTiger.turtle

WiredTiger.wt



 Comments   
Comment by John Narma [ 03/Dec/18 ]

Thanks for reply.

I deleted journal files and started with version 3.4.8. The problem is solved.

Thank you very much.

Comment by Danny Hatcher (Inactive) [ 30/Nov/18 ]

Hello John,

The repair functionality actually runs before any kind of version checks. The logs indicate that repair fixed the corruption then cleanly exited because oof the version. If you start the data files now with the original 3.4.8 binaries, does everything work? If you receive an "unsupported WiredTiger file version" error, please delete the journal files and try to start the process again.

Thank you,

Danny

Comment by John Narma [ 29/Nov/18 ]

Thanks for your help.

In my environment, the mongoDB is single-node. So I tried run "mongod --repair" (before trying it, I took a full-copy of dbpath) but repair didn't work.

I also tried in version 3.6 and latest(4.0.4).

 In version 4.0.4, mongod says

mongo_1 | 2018-11-29T07:03:09.784+0000 F CONTROL [initandlisten] ** IMPORTANT: UPGRADE PROBLEM: The data files need to be fully upgraded to version 3.6 before attempting an upgrade to 4.0; see http://dochub.mongodb.org/core/4.0-upgrade-fcv for more details.

Can I upgrade my data file to version 3.6 with mongod not running?

Thank you.

mongod_--repair_v3.4.txt

mongod_--repair_v3.6.txt

mongod_--repair_v4.0.4.txt

 

Comment by Danny Hatcher (Inactive) [ 28/Nov/18 ]

Hello,

To resolve this issue, I would recommend a clean resync from a node that is not affected. If that is not possible, I would recommend executing repairDatabase.

Thank you,

Danny

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