[SERVER-25367]  WT_ERROR: non-specific WiredTiger error, terminating Created: 01/Aug/16  Updated: 02/Feb/22  Resolved: 04/Oct/16

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

Type: Bug Priority: Major - P3
Reporter: Tsedendamba Assignee: Kelsey Schubert
Resolution: Done Votes: 0
Labels: envns, rpo, trcf, wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: HTML File WiredTiger     File WiredTiger.lock     File WiredTiger.turtle     File WiredTigerLAS.wt    
Issue Links:
Problem/Incident
causes TOOLS-3037 My MongoDB cannot be started through ... Closed
Operating System: Windows
Participants:

 Description   

2016-08-01T14:32:01.966+0900 I CONTROL  [initandlisten] MongoDB starting : pid=9752 port=27017 dbpath=C:\data\db\ 64-bit host=unlimited1
2016-08-01T14:32:01.971+0900 I CONTROL  [initandlisten] targetMinOS: Windows 7/Windows Server 2008 R2
2016-08-01T14:32:01.975+0900 I CONTROL  [initandlisten] db version v3.2.6
2016-08-01T14:32:01.977+0900 I CONTROL  [initandlisten] git version: 05552b562c7a0b3143a729aaa0838e558dc49b25
2016-08-01T14:32:01.994+0900 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1p-fips 9 Jul 2015
2016-08-01T14:32:01.998+0900 I CONTROL  [initandlisten] allocator: tcmalloc
2016-08-01T14:32:02.003+0900 I CONTROL  [initandlisten] modules: none
2016-08-01T14:32:02.007+0900 I CONTROL  [initandlisten] build environment:
2016-08-01T14:32:02.018+0900 I CONTROL  [initandlisten]     distmod: 2008plus-ssl
2016-08-01T14:32:02.023+0900 I CONTROL  [initandlisten]     distarch: x86_64
2016-08-01T14:32:02.027+0900 I CONTROL  [initandlisten]     target_arch: x86_64
2016-08-01T14:32:02.032+0900 I CONTROL  [initandlisten] options: {}
2016-08-01T14:32:02.036+0900 I -        [initandlisten] Detected data files in C:\data\db\ created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2016-08-01T14:32:02.061+0900 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=6G,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),
2016-08-01T14:32:02.100+0900 E STORAGE  [initandlisten] WiredTiger (-31802) [1470029522:100213][9752:140706184410208], file:WiredTiger.wt, connection: WiredTiger.wt: handle-read: ReadFile: failed to read 4096 bytes at offset 0: WT_ERROR: non-specific WiredTiger error
2016-08-01T14:32:02.121+0900 I -        [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error
2016-08-01T14:32:02.127+0900 I STORAGE  [initandlisten] exception in initAndListen: 28595 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2016-08-01T14:32:02.149+0900 I CONTROL  [initandlisten] dbexit:  rc: 100



 Comments   
Comment by Kelsey Schubert [ 04/Oct/16 ]

Hi tsedendamba,

Sorry for the silence, we've been discussing whether there is anything more that we can do in this situation. Unfortunately, it appears that the power failure lead to file system corruption, which affected the MongoDB data files. In this situation, there is little that MongoDB can do other than report that the files have become corrupted.

Kind regards,
Thomas

Comment by Tsedendamba [ 02/Aug/16 ]

I using windows 10. Unplanned power outage and unclean shutdown. After mongodb not started. My storage device is SATA. I don't now how to check file health. How to check file? My db path is c:/data/db default path.

mongod --repair command after that log

C:\Users\1>mongod -repair
2016-08-02T09:28:05.735+0900 I CONTROL [initandlisten] MongoDB starting : pid=9700 port=27017 dbpath=C:\data\db\ 64-bit host=unlimited2
2016-08-02T09:28:05.735+0900 I CONTROL [initandlisten] targetMinOS: Windows 7/Windows Server 2008 R2
2016-08-02T09:28:05.736+0900 I CONTROL [initandlisten] db version v3.2.8
2016-08-02T09:28:05.736+0900 I CONTROL [initandlisten] git version: ed70e33130c977bda0024c125b56d159573dbaf0
2016-08-02T09:28:05.736+0900 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1p-fips 9 Jul 2015
2016-08-02T09:28:05.736+0900 I CONTROL [initandlisten] allocator: tcmalloc
2016-08-02T09:28:05.736+0900 I CONTROL [initandlisten] modules: none
2016-08-02T09:28:05.736+0900 I CONTROL [initandlisten] build environment:
2016-08-02T09:28:05.736+0900 I CONTROL [initandlisten] distmod: 2008plus-ssl
2016-08-02T09:28:05.736+0900 I CONTROL [initandlisten] distarch: x86_64
2016-08-02T09:28:05.736+0900 I CONTROL [initandlisten] target_arch: x86_64
2016-08-02T09:28:05.736+0900 I CONTROL [initandlisten] options:

{ repair: true }

2016-08-02T09:28:05.738+0900 I - [initandlisten] Detected data files in C:\data\db\ created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2016-08-02T09:28:05.739+0900 I STORAGE [initandlisten] Detected WT journal files. Running recovery from last checkpoint.
2016-08-02T09:28:05.739+0900 I STORAGE [initandlisten] journal to nojournal transition config: create,cache_size=6G,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),
2016-08-02T09:28:05.919+0900 E STORAGE [initandlisten] WiredTiger (-31803) [1470097685:919139][9700:140709337585360], txn-recover: Recovery failed: WT_NOTFOUND: item not found
2016-08-02T09:28:05.938+0900 I - [initandlisten] Assertion: 28718:-31803: WT_NOTFOUND: item not found
2016-08-02T09:28:05.938+0900 I STORAGE [initandlisten] exception in initAndListen: 28718 -31803: WT_NOTFOUND: item not found, terminating
2016-08-02T09:28:05.938+0900 I CONTROL [initandlisten] dbexit: rc: 100

Comment by Ramon Fernandez Marina [ 01/Aug/16 ]

Sorry you've run into this issues tsedendamba. You're getting this message because the WiredTiger.wt file got corrupted. Can you please provide more details on the events leading up to this problem? For example, did you have any unclean shutdowns?

Note also the file corruption may be caused by an unhealthy storage layer. What type of storage devices are you using? Have you check their health recently?

If you can upload full logs for this node as well as a full directory listing of the contents of your dbpath that may also help with the investigation.

Thanks,
Ramón.

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