[SERVER-48087] WiredTiger has failed to open its metadata Created: 11/May/20  Updated: 11/May/20  Resolved: 11/May/20

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

Type: Bug Priority: Major - P3
Reporter: Robert Breilich Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Hi,

we had a crash with our storage infrastucture today, why we had to restore a backup. Unfortunately it (or all backups tested so far) threw errors. We are running Version 3.4.x inside docker.

 

2020-05-11T14:54:35.701+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=mongodb-prod-78b55857b-hppvg 2020-05-11T14:54:35.701+0000 I CONTROL  [initandlisten] db version v3.4.23 2020-05-11T14:54:35.701+0000 I CONTROL  [initandlisten] git version: 324017ede1dbb1c9554dd2dceb15f8da3c59d0e8 2020-05-11T14:54:35.701+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016 2020-05-11T14:54:35.701+0000 I CONTROL  [initandlisten] allocator: tcmalloc 2020-05-11T14:54:35.701+0000 I CONTROL  [initandlisten] modules: none 2020-05-11T14:54:35.701+0000 I CONTROL  [initandlisten] build environment: 2020-05-11T14:54:35.701+0000 I CONTROL  [initandlisten]     distmod: ubuntu1604 2020-05-11T14:54:35.701+0000 I CONTROL  [initandlisten]     distarch: x86_64 2020-05-11T14:54:35.701+0000 I CONTROL  [initandlisten]     target_arch: x86_64 2020-05-11T14:54:35.701+0000 I CONTROL  [initandlisten] options: { net: { bindIp: "0.0.0.0" }, replication: { replSet: "mobile" }, security: { authorization: "enabled" }, storage: { wiredTiger: { engineConfig: { cacheSizeGB: 10.0 } } } } 2020-05-11T14:54:35.701+0000 W -        [initandlisten] Detected unclean shutdown - /data/db/mongod.lock is not empty. 2020-05-11T14:54:35.705+0000 I -        [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. 2020-05-11T14:54:35.705+0000 W STORAGE  [initandlisten] Recovering data from the last clean checkpoint. 2020-05-11T14:54:35.705+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=10240M,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),verbose=(recovery_progress), 2020-05-11T14:54:35.709+0000 E STORAGE  [initandlisten] WiredTiger error (-31802) [1589208875:709730][1:0x7f56fefe8d40], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error 2020-05-11T14:54:35.709+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1589208875:709760][1:0x7f56fefe8d40], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata 2020-05-11T14:54:35.709+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1589208875:709767][1:0x7f56fefe8d40], 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 2020-05-11T14:54:35.709+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1589208875:709773][1:0x7f56fefe8d40], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options 2020-05-11T14:54:35.709+0000 I -        [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 277 2020-05-11T14:54:35.710+0000 I STORAGE  [initandlisten] exception in initAndListen: 28595 -31802: WT_ERROR: non-specific WiredTiger error, terminating 2020-05-11T14:54:35.710+0000 I NETWORK  [initandlisten] shutdown: going to close listening sockets... 2020-05-11T14:54:35.710+0000 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-27017.sock 2020-05-11T14:54:35.710+0000 I NETWORK  [initandlisten] shutdown: going to flush diaglog... 2020-05-11T14:54:35.710+0000 I CONTROL  [initandlisten] now exiting 2020-05-11T14:54:35.710+0000 I CONTROL  [initandlisten] shutting down with code:100
 



 Comments   
Comment by Carl Champain (Inactive) [ 11/May/20 ]

Hi robert.breilich@geomagic.world,

MongoDB 3.4 is already end-of-lifed, which means it is unsupported by us. We strongly recommend you upgrade to a supported version. If you need assistance troubleshooting, I encourage you to ask our community by posting on the MongoDB Community Forums or on Stack Overflow with the mongodb tag.

Kind regards,
Carl
 

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