[SERVER-63242] Unable to read root page from file:WiredTiger.wt Created: 03/Feb/22  Updated: 03/Mar/22  Resolved: 03/Mar/22

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

Type: Bug Priority: Major - P3
Reporter: Jyanon Rei Assignee: Edwin Zhou
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    
Operating System: ALL
Participants:

 Description   

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,

 

 



 Comments   
Comment by Edwin Zhou [ 03/Mar/22 ]

Hi 804173948@qq.com,

We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Best,
Edwin

Comment by Edwin Zhou [ 22/Feb/22 ]

Hi 804173948@qq.com,

We still need additional information to diagnose the problem. If this is still an issue for you, would you please first make a complete copy of the database's $dbpath directory to safeguard so that you can work off of the current $dbpath, then try mongod --repair using the latest version of MongoDB?

In the event that a --repair operation is unsuccessful, then please also provide:

  • The logs leading up to the first occurrence of any issue
  • The logs of the repair operation.
  • The logs of any attempt to start mongod after the repair operation completed.

Best,
Edwin

Comment by Edwin Zhou [ 03/Feb/22 ]

Hi 804173948@qq.com,

MongoDB v3.2 reached end of life in December 2018 and is no longer supported. But we can provide limited guidance on this issue. The ideal resolution is to perform a clean resync from an unaffected node.
First, make a complete copy of the database's $dbpath directory to safeguard so that you can work off of the current $dbpath. Then, try mongod --repair using the latest version of MongoDB.

Best,
Edwin

Generated at Thu Feb 08 05:57:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.