[SERVER-44691] unable to read root page from file:WiredTiger.wt Created: 18/Nov/19  Updated: 25/Feb/20  Resolved: 25/Feb/20

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

Type: Bug Priority: Major - P3
Reporter: Lin deli Assignee: Carl Champain (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

2019-11-18T14:23:40.546+0800 I CONTROL  [initandlisten] MongoDB starting : pid=5661 port=27017 dbpath=/usr/local/mongodb/data 64-bit host=PheiOS
 
2019-11-18T14:23:40.546+0800 I CONTROL  [initandlisten] db version v3.6.1
 
2019-11-18T14:23:40.546+0800 I CONTROL  [initandlisten] git version: 025d4f4fe61efd1fb6f0005be20cb45a004093d1
 
2019-11-18T14:23:40.546+0800 I CONTROL  [initandlisten] allocator: tcmalloc
 
2019-11-18T14:23:40.546+0800 I CONTROL  [initandlisten] modules: none
 
2019-11-18T14:23:40.546+0800 I CONTROL  [initandlisten] build environment:
 
2019-11-18T14:23:40.546+0800 I CONTROL  [initandlisten]     distarch: x86_64
 
2019-11-18T14:23:40.546+0800 I CONTROL  [initandlisten]     target_arch: x86_64
 
2019-11-18T14:23:40.546+0800 I CONTROL  [initandlisten] options: \{ config: "/usr/local/mongodb/mongod.conf", net: { bindIp: "0.0.0.0", port: 27017 }, processManagement: \{ fork: false, pidFilePath: "/var/run/mongod.pid" }, repair: true, storage: \{ dbPath: "/usr/local/mongodb/data", journal: { enabled: false } }, systemLog: \{ destination: "file", logAppend: false, path: "/var/log/mongod.log" } }
 
2019-11-18T14:23:40.546+0800 I -        [initandlisten] Detected data files in /usr/local/mongodb/data created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
 
2019-11-18T14:23:40.547+0800 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=3478M,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),statistics_log=(wait=0),verbose=(recovery_progress),,log=(enabled=false),
 
2019-11-18T14:23:40.553+0800 E STORAGE  [initandlisten] WiredTiger error (-31802) [1574058220:553550][5661:0x7fbab403d9c0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
 
2019-11-18T14:23:40.553+0800 E STORAGE  [initandlisten] WiredTiger error (0) [1574058220:553606][5661:0x7fbab403d9c0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
 
2019-11-18T14:23:40.553+0800 E STORAGE  [initandlisten] WiredTiger error (0) [1574058220:553619][5661:0x7fbab403d9c0], 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
 
2019-11-18T14:23:40.553+0800 E STORAGE  [initandlisten] WiredTiger error (0) [1574058220:553632][5661:0x7fbab403d9c0], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
 
2019-11-18T14:23:40.554+0800 E -        [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 413
 
2019-11-18T14:23:40.554+0800 I STORAGE  [initandlisten] exception in initAndListen: Location28595: -31802: WT_ERROR: non-specific WiredTiger error, terminating
 
2019-11-18T14:23:40.554+0800 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
 
2019-11-18T14:23:40.554+0800 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-27017.sock
 
2019-11-18T14:23:40.554+0800 I CONTROL  [initandlisten] now exiting
 
2019-11-18T14:23:40.555+0800 I CONTROL  [initandlisten] shutting down with code:100



 Comments   
Comment by Carl Champain (Inactive) [ 25/Feb/20 ]

Hi,

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

Regards,
Carl

Comment by Carl Champain (Inactive) [ 04/Dec/19 ]

Hi 654815099@qq.com,

Any updates on this issue?

Comment by Carl Champain (Inactive) [ 18/Nov/19 ]

Hi 654815099@qq.com,

Thanks for the report.
Please make a complete copy of the database's $dbpath directory and safeguard that copy. Could you please download the 4.0.12 MongoDB binaries, use the 4.0.12 binary to run mongod --repair against your data files, and then start the mongod using your original binaries?

Kind regards,
Carl

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