[SERVER-34084] WiredTiger.wt file corrupted and cannot recover Created: 23/Mar/18  Updated: 23/Apr/18  Resolved: 27/Mar/18

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

Type: Bug Priority: Major - P3
Reporter: sharmila Assignee: Kelsey Schubert
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu trusty 14.04, Mongo version 3.2.19


Attachments: File WiredTiger.turtle     File WiredTiger.wt    
Participants:

 Description   

My mongodb data got corrupted and I couldn't restore it. Kindly help me to restore the datas.

Error:
2018-03-23T16:50:44.490+0530 I - [initandlisten] Detected data files in /var/lib/mongodata created by the 'wiredTiger' storage engine, so setting the$
2018-03-23T16:50:44.491+0530 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=8G,session_max=20000,eviction=(threads_min=4,threads_max=4$
2018-03-23T16:50:44.520+0530 E STORAGE [initandlisten] WiredTiger (-31802) [1521804044:520514][5696:0x7f26780eccc0], txn-recover: unsupported WiredTiger fi$
2018-03-23T16:50:44.520+0530 E STORAGE [initandlisten] WiredTiger (0) [1521804044:520594][5696:0x7f26780eccc0], txn-recover: WiredTiger is unable to read t$
2018-03-23T16:50:44.520+0530 E STORAGE [initandlisten] WiredTiger (0) [1521804044:520618][5696:0x7f26780eccc0], txn-recover: This may be due to the log fil$
2018-03-23T16:50:44.520+0530 E STORAGE [initandlisten] WiredTiger (0) [1521804044:520639][5696:0x7f26780eccc0], txn-recover: You should confirm that you ha$
2018-03-23T16:50:44.520+0530 E STORAGE [initandlisten] WiredTiger (-31802) [1521804044:520668][5696:0x7f26780eccc0], txn-recover: Recovery failed: WT_ERROR$
2018-03-23T16:50:44.524+0530 I - [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error
2018-03-23T16:50:44.524+0530 I STORAGE [initandlisten] exception in initAndListen: 28595 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2018-03-23T16:50:44.524+0530 I CONTROL [initandlisten] dbexit: rc: 100



 Comments   
Comment by sharmila [ 27/Mar/18 ]

Hi Kelsey T Schubert,
Thank you so much. After updating to the latest version it got to work.

Comment by sharmila [ 27/Mar/18 ]

Sure, Let me check and update it now.

Comment by Kelsey Schubert [ 27/Mar/18 ]

Hi sharmila,

This error generally indicates that the files were on a mongod running with feature compatibility version 3.6. What do the logs show if you start with with the latest version of mongod, MongoDB 3.6.3?

Thanks,
Kelsey

Comment by sharmila [ 27/Mar/18 ]

Hi Kelsey T Schubert,
Can you please help me on this issue. It's very emergency. I even tired mongod repair but didn't work..

Comment by sharmila [ 26/Mar/18 ]

Here is the full log :

2018-03-26T12:18:28.594+0530 I CONTROL [main] ***** SERVER RESTARTED *****
2018-03-26T12:18:28.603+0530 I CONTROL [initandlisten] MongoDB starting : pid=2252 port=6987 dbpath=/var/lib/mongodata 64-bit host=iptv
2018-03-26T12:18:28.603+0530 I CONTROL [initandlisten] db version v3.2.19
2018-03-26T12:18:28.603+0530 I CONTROL [initandlisten] git version: a9f574de6a566a58b24d126b44a56718d181e989
2018-03-26T12:18:28.603+0530 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1f 6 Jan 2014
2018-03-26T12:18:28.603+0530 I CONTROL [initandlisten] allocator: tcmalloc
2018-03-26T12:18:28.603+0530 I CONTROL [initandlisten] modules: none
2018-03-26T12:18:28.603+0530 I CONTROL [initandlisten] build environment:
2018-03-26T12:18:28.603+0530 I CONTROL [initandlisten] distmod: ubuntu1404
2018-03-26T12:18:28.603+0530 I CONTROL [initandlisten] distarch: x86_64
2018-03-26T12:18:28.603+0530 I CONTROL [initandlisten] target_arch: x86_64
2018-03-26T12:18:28.603+0530 I CONTROL [initandlisten] options: { config: "/etc/mongod.conf", net:

{ bindIp: "127.0.0.1", port: 6987 }

, security:

{ authorization: "enabled" }

, storage: { dbPath: "/var/lib/mongodata", journal:

{ enabled: true }

}, systemLog:

{ destination: "file", logAppend: true, path: "/var/log/mongodb/mongod.log" }

}
2018-03-26T12:18:28.657+0530 I - [initandlisten] Detected data files in /var/lib/mongodata created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2018-03-26T12:18:28.657+0530 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=8G,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),
2018-03-26T12:18:28.702+0530 E STORAGE [initandlisten] WiredTiger (-31802) [1522046908:702792][2252:0x7f59144e8cc0], txn-recover: unsupported WiredTiger file version: this build only supports major/minor versions up to 1/0, and the file is version 2/0: WT_ERROR: non-specific WiredTiger error
2018-03-26T12:18:28.702+0530 E STORAGE [initandlisten] WiredTiger (0) [1522046908:702873][2252:0x7f59144e8cc0], txn-recover: WiredTiger is unable to read the recovery log.
2018-03-26T12:18:28.702+0530 E STORAGE [initandlisten] WiredTiger (0) [1522046908:702907][2252:0x7f59144e8cc0], txn-recover: This may be due to the log files being encrypted, being from an older version or due to corruption on disk
2018-03-26T12:18:28.702+0530 E STORAGE [initandlisten] WiredTiger (0) [1522046908:702930][2252:0x7f59144e8cc0], txn-recover: You should confirm that you have opened the database with the correct options including all encryption and compression options
2018-03-26T12:18:28.702+0530 E STORAGE [initandlisten] WiredTiger (-31802) [1522046908:702960][2252:0x7f59144e8cc0], txn-recover: Recovery failed: WT_ERROR: non-specific WiredTiger error
2018-03-26T12:18:28.706+0530 I - [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error
2018-03-26T12:18:28.706+0530 I STORAGE [initandlisten] exception in initAndListen: 28595 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2018-03-26T12:18:28.706+0530 I CONTROL [initandlisten] dbexit: rc: 100

Comment by Kelsey Schubert [ 23/Mar/18 ]

Hi sharmila,

It looks like the logs got cut off after a certain line length. Would you please upload the complete logs from when the mongod instance was first started?

Thank you,
Kelsey

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