[SERVER-40204] : WT_ERROR: non-specific WiredTiger error Created: 19/Mar/19  Updated: 07/Nov/22  Resolved: 21/Mar/19

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

Type: Bug Priority: Major - P3
Reporter: Chang Hsin Ting Assignee: Danny Hatcher (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows Server 2012


Attachments: HTML File WiredTiger     File WiredTiger.turtle     File WiredTiger.wt     File logs.txt.2019-03-18T08-47-13    
Issue Links:
Duplicate
is duplicated by SERVER-71116 Because of I/O device error, unable t... Closed
Operating System: ALL
Steps To Reproduce:

when I restarted mongoDB,it can ran.
But we want to know why it aborted. thank!

Participants:

 Description   

2019-03-10T13:58:51.070+0800 I NETWORK [conn362] received client metadata from 127.0.0.1:49846 conn362: \{ driver: { name: "mongo-csharp-driver", version: "2.4.3.23" }, os: \{ type: "Windows", name: "Microsoft Windows 6.3.9600", architecture: "x86_32", version: "6.3.9600" }, platform: ".NET Framework 4.0.0.0" }
2019-03-10T13:58:51.137+0800 I ACCESS [conn362] Successfully authenticated as principal dds on CPPS
2019-03-10T14:16:11.867+0800 I NETWORK [conn361] end connection 127.0.0.1:65259 (2 connections now open)
2019-03-10T14:21:45.562+0800 E STORAGE [WTJournalFlusher] WiredTiger error (-31802) [1552198905:561554][1136:140737077055616], WT_SESSION.log_flush: c:\Mongodb\journal\WiredTigerLog.0000000890 handle-sync: FlushFileBuffers: ǝ̰ I/O ً٭࠹ܾʒƈ֌˫ѵǦސɄƒ 
: WT_ERROR: non-specific WiredTiger error
2019-03-10T14:21:45.562+0800 F - [WTJournalFlusher] Invariant failure: _waitUntilDurableSession->log_flush(_waitUntilDurableSession, "sync=on") resulted in status UnknownError: -31802: WT_ERROR: non-specific WiredTiger error at src\mongo\db\storage\wiredtiger\wiredtiger_session_cache.cpp 279
2019-03-10T14:21:45.562+0800 F - [WTJournalFlusher]
 
***aborting after invariant() failure
 
 
2019-03-10T14:26:57.924+0800 I CONTROL [WTJournalFlusher] mongod.exe ...\src\mongo\util\stacktrace_windows.cpp(244) mongo::printStackTrace+0x67x
2019-03-10T14:26:57.924+0800 I CONTROL [WTJournalFlusher] mongod.exe ...\src\mongo\util\signal_handlers_synchronous.cpp(182) mongo::`anonymous namespace'::printSignalAndBacktrace+0x116x
2019-03-10T14:26:57.924+0800 I CONTROL [WTJournalFlusher] mongod.exe ...\src\mongo\util\signal_handlers_synchronous.cpp(238) mongo::`anonymous namespace'::abruptQuit+0x133x
2019-03-10T14:26:57.924+0800 I CONTROL [WTJournalFlusher] ucrtbase.DLL raise+0x488x
2019-03-10T14:26:57.924+0800 I CONTROL [WTJournalFlusher] ucrtbase.DLL abort+0x49x
2019-03-10T14:26:57.925+0800 I CONTROL [WTJournalFlusher] mongod.exe ...\src\mongo\util\assert_util.cpp(152) mongo::invariantOKFailed+0x552x
2019-03-10T14:26:57.925+0800 I CONTROL [WTJournalFlusher] mongod.exe ...\src\mongo\db\storage\wiredtiger\wiredtiger_session_cache.cpp(279) mongo::WiredTigerSessionCache::waitUntilDurable+0x913x
2019-03-10T14:26:57.925+0800 I CONTROL [WTJournalFlusher] mongod.exe ...\src\mongo\db\storage\wiredtiger\wiredtiger_kv_engine.cpp(116) mongo::WiredTigerKVEngine::WiredTigerJournalFlusher::run+0x654x
2019-03-10T14:26:57.925+0800 I CONTROL [WTJournalFlusher] mongod.exe ...\src\mongo\util\background.cpp(150) mongo::BackgroundJob::jobBody+0x305x
2019-03-10T14:26:57.925+0800 I CONTROL [WTJournalFlusher] mongod.exe c:\program files (x86)\microsoft visual studio 14.0\vc\include\thr\xthread(247) std::_LaunchPad<std::unique_ptr<std::tuple<std::_Binder<std::_Unforced,void (__cdecl mongo::BackgroundJob::*)(void) __ptr64,mongo::BackgroundJob * __ptr64 const> >,std::default_delete<std::tuple<std::_Binder<std::_Unforced,void (__cdecl mongo::BackgroundJob::*)(void) __ptr64,mongo::BackgroundJob * __ptr64 const> > > > >::_Run+0x117x
2019-03-10T14:26:57.925+0800 I CONTROL [WTJournalFlusher] mongod.exe c:\program files (x86)\microsoft visual studio 14.0\vc\include\thr\xthread(210) std::_Pad::_Call_func+0x9x
2019-03-10T14:26:57.925+0800 I CONTROL [WTJournalFlusher] ucrtbase.DLL crt_at_quick_exit+0x125x
2019-03-10T14:26:57.925+0800 I CONTROL [WTJournalFlusher] KERNEL32.DLL BaseThreadInitThunk+0x34x
2019-03-10T14:26:57.925+0800 F - [WTJournalFlusher] Got signal: 22 (SIGABRT).
2019-03-10T14:26:57.926+0800 F CONTROL [WTJournalFlusher] *** unhandled exception 0x0000000E at 0x00007FFFE5DD8B9C, terminating
2019-03-10T14:26:57.926+0800 F CONTROL [WTJournalFlusher] *** stack trace for unhandled exception:
2019-03-10T14:26:57.937+0800 I CONTROL [WTJournalFlusher] KERNELBASE.dll RaiseException+0x108x
2019-03-10T14:26:57.937+0800 I CONTROL [WTJournalFlusher] mongod.exe ...\src\mongo\util\signal_handlers_synchronous.cpp(239) mongo::`anonymous namespace'::abruptQuit+0x157x
2019-03-10T14:26:57.937+0800 I CONTROL [WTJournalFlusher] ucrtbase.DLL raise+0x488x
2019-03-10T14:26:57.937+0800 I CONTROL [WTJournalFlusher] ucrtbase.DLL abort+0x49x
2019-03-10T14:26:57.937+0800 I CONTROL [WTJournalFlusher] mongod.exe ...\src\mongo\util\assert_util.cpp(152) mongo::invariantOKFailed+0x552x
2019-03-10T14:26:57.937+0800 I CONTROL [WTJournalFlusher] mongod.exe ...\src\mongo\db\storage\wiredtiger\wiredtiger_session_cache.cpp(279) mongo::WiredTigerSessionCache::waitUntilDurable+0x913x
2019-03-10T14:26:57.937+0800 I CONTROL [WTJournalFlusher] mongod.exe ...\src\mongo\db\storage\wiredtiger\wiredtiger_kv_engine.cpp(116) mongo::WiredTigerKVEngine::WiredTigerJournalFlusher::run+0x654x
2019-03-10T14:26:57.937+0800 I CONTROL [WTJournalFlusher] mongod.exe ...\src\mongo\util\background.cpp(150) mongo::BackgroundJob::jobBody+0x305x
2019-03-10T14:26:57.937+0800 I CONTROL [WTJournalFlusher] mongod.exe c:\program files (x86)\microsoft visual studio 14.0\vc\include\thr\xthread(247) std::_LaunchPad<std::unique_ptr<std::tuple<std::_Binder<std::_Unforced,void (__cdecl mongo::BackgroundJob::*)(void) __ptr64,mongo::BackgroundJob * __ptr64 const> >,std::default_delete<std::tuple<std::_Binder<std::_Unforced,void (__cdecl mongo::BackgroundJob::*)(void) __ptr64,mongo::BackgroundJob * __ptr64 const> > > > >::_Run+0x117x
2019-03-10T14:26:57.937+0800 I CONTROL [WTJournalFlusher] mongod.exe c:\program files (x86)\microsoft visual studio 14.0\vc\include\thr\xthread(210) std::_Pad::_Call_func+0x9x
2019-03-10T14:26:57.937+0800 I CONTROL [WTJournalFlusher] ucrtbase.DLL crt_at_quick_exit+0x125x
2019-03-10T14:26:57.937+0800 I CONTROL [WTJournalFlusher] KERNEL32.DLL BaseThreadInitThunk+0x34x
2019-03-10T14:26:57.937+0800 I - [WTJournalFlusher] 
2019-03-10T14:29:12.017+0800 I NETWORK [conn362] end connection 127.0.0.1:49846 (1 connection now open)
2019-03-10T14:33:04.785+0800 I NETWORK [listener] connection accepted from 127.0.0.1:50612 #363 (2 connections now open)
2019-03-10T14:33:04.786+0800 I NETWORK [conn363] received client metadata from 127.0.0.1:50612 conn363: \{ driver: { name: "mongo-csharp-driver", version: "2.4.3.23" }, os: \{ type: "Windows", name: "Microsoft Windows 6.3.9600", architecture: "x86_32", version: "6.3.9600" }, platform: ".NET Framework 4.0.0.0" }
2019-03-10T14:33:04.856+0800 I ACCESS [conn363] Successfully authenticated as principal dds on CPPS
2019-03-10T14:34:15.186+0800 E STORAGE [WTCheckpointThread] WiredTiger error (-31802) [1552199655:185726][1136:140737077055616], WT_SESSION.checkpoint: c:\Mongodb\journal\WiredTigerLog.0000000890 handle-sync: FlushFileBuffers: ǝ̰ I/O ً٭࠹ܾʒƈ֌˫ѵǦސɄƒ 
: WT_ERROR: non-specific WiredTiger error
2019-03-10T14:34:15.186+0800 F - [WTCheckpointThread] Invariant failure: s->checkpoint(s, nullptr) resulted in status UnknownError: -31802: WT_ERROR: non-specific WiredTiger error at src\mongo\db\storage\wiredtiger\wiredtiger_kv_engine.cpp 176
2019-03-10T14:34:15.186+0800 F - [WTCheckpointThread]
 
***aborting after invariant() failure



 Comments   
Comment by Danny Hatcher (Inactive) [ 21/Mar/19 ]

Hello,

It is likely that the problem is due to the disk errors that you are seeing. Unfortunately there is nothing further that we can do from our side but I am glad to hear that the server is now running correctly.

Thanks,

Danny

Comment by Chang Hsin Ting [ 21/Mar/19 ]

Hi,

Thank for your response.When we restarted it,there was no error message again.I see some ntfs and disk error on Windows' event at the time of the crash.

Thanks,

Comment by Danny Hatcher (Inactive) [ 20/Mar/19 ]

Hello,

We've discussed this error internally. The error occurred due to the WiredTiger journal being unable to correctly flush its data to disk. Unfortunately, there is no explanation in the logs that indicate why it happened in the first place. If you check the system logs at the time of the crash, is there anything that explains from Windows' perspective why a disk write may have failed?

Is your node back up and running correctly or are you still struggling to restart it?

Thanks,

Danny

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