|
Hi Team,
I am using MongoDB version 4.0 and getting the same error. Can you pls Help me why this error got occurred.
2021-07-23T19:05:26.900+0530 E STORAGE [WTCheckpointThread] WiredTiger error (13) [1627047326:876858][1540:140704437702784], file:ReconDB_UAT/collection/26--5782211086932514962.wt, WT_SESSION.checkpoint: __win_open_file, 543: D:\MongoData\Data\ReconDB_UAT/collection/26--5782211086932514962.wt: handle-open: CreateFileW: Access is denied.
: Permission denied Raw: [1627047326:876858][1540:140704437702784], file:ReconDB_UAT/collection/26--5782211086932514962.wt, WT_SESSION.checkpoint: __win_open_file, 543: D:\MongoData\Data\ReconDB_UAT/collection/26--5782211086932514962.wt: handle-open: CreateFileW: Access is denied.
: Permission denied
2021-07-23T19:05:26.900+0530 F - [WTCheckpointThread] Invariant failure: s->checkpoint(s, "use_timestamp=true") resulted in status UnknownError: 13: Permission denied at src\mongo\db\storage\wiredtiger\wiredtiger_kv_engine.cpp 352
2021-07-23T19:05:26.900+0530 F - [WTCheckpointThread]
***aborting after invariant() failure
2021-07-23T19:05:28.595+0530 I ASIO [Replication] Connecting to ArbHost:27017
2021-07-23T19:05:28.642+0530 I ASIO [Replication] Failed to connect to ArbHost:27017 - AuthenticationFailed: Authentication failed.
2021-07-23T19:05:28.642+0530 I CONNPOOL [Replication] Dropping all pooled connections to ArbHost:27017 due to AuthenticationFailed: Authentication failed.
2021-07-23T19:05:28.642+0530 I REPL_HB [replexec-99] Error in heartbeat (requestId: 1211726) to ArbHost:27017, response status: AuthenticationFailed: Authentication failed.
2021-07-23T19:05:30.643+0530 I ASIO [Replication] Connecting to ArbHost:27017
2021-07-23T19:05:30.689+0530 I ASIO [Replication] Failed to connect to ArbHost:27017 - AuthenticationFailed: Authentication failed.
2021-07-23T19:05:30.689+0530 I CONNPOOL [Replication] Dropping all pooled connections to ArbHost:27017 due to AuthenticationFailed: Authentication failed.
2021-07-23T19:05:30.690+0530 I REPL_HB [replexec-99] Error in heartbeat (requestId: 1211729) to ArbHost:27017, response status: AuthenticationFailed: Authentication failed.
2021-07-23T19:05:32.691+0530 I ASIO [Replication] Connecting to ArbHost:27017
2021-07-23T19:05:32.736+0530 I ASIO [Replication] Failed to connect to ArbHost:27017 - AuthenticationFailed: Authentication failed.
2021-07-23T19:05:32.736+0530 I CONNPOOL [Replication] Dropping all pooled connections to ArbHost:27017 due to AuthenticationFailed: Authentication failed.
2021-07-23T19:05:32.736+0530 I REPL_HB [replexec-99] Error in heartbeat (requestId: 1211732) to ArbHost:27017, response status: AuthenticationFailed: Authentication failed.
2021-07-23T19:05:32.952+0530 F - [WTCheckpointThread] Got signal: 22 (SIGABRT).
mongod.exe ...\src\mongo\util\stacktrace_windows.cpp(247) mongo::printStackTrace+0x43
mongod.exe ...\src\mongo\util\signal_handlers_synchronous.cpp(184) mongo::`anonymous namespace'::printSignalAndBacktrace+0x74
mongod.exe ...\src\mongo\util\signal_handlers_synchronous.cpp(240) mongo::`anonymous namespace'::abruptQuit+0x85
ucrtbase.DLL raise+0x1e7
ucrtbase.DLL abort+0x31
mongod.exe ...\src\mongo\util\assert_util.cpp(129) mongo::invariantOKFailed+0x228
mongod.exe ...\src\mongo\db\storage\wiredtiger\wiredtiger_kv_engine.cpp(352) mongo::WiredTigerKVEngine::WiredTigerCheckpointThread::run+0x661
mongod.exe ...\src\mongo\util\background.cpp(153) mongo::BackgroundJob::jobBody+0x131
mongod.exe c:\program files (x86)\microsoft visual studio 14.0\vc\include\thr\xthread(247) std::_LaunchPad<std::unique_ptr<std::tuple<<lambda_8929d5e2502e4de5883694c1a7a329eb> >,std::default_delete<std::tuple<<lambda_8929d5e2502e4de5883694c1a7a329eb> > > > >::_Run+0x77
mongod.exe c:\program files (x86)\microsoft visual studio 14.0\vc\include\thr\xthread(210) std::_Pad::_Call_func+0x9
ucrtbase.DLL o__realloc_base+0x60
KERNEL32.DLL BaseThreadInitThunk+0x22
2021-07-23T19:05:33.006+0530 F CONTROL [WTCheckpointThread] *** unhandled exception 0x0000000E at 0x00007FF84DC27AFC, terminating
2021-07-23T19:05:33.006+0530 F CONTROL [WTCheckpointThread] *** stack trace for unhandled exception:
2021-07-23T19:05:33.021+0530 I - [WTCheckpointThread] KERNELBASE.dll RaiseException+0x6c
mongod.exe ...\src\mongo\util\signal_handlers_synchronous.cpp(241) mongo::`anonymous namespace'::abruptQuit+0x9d
ucrtbase.DLL raise+0x1e7
ucrtbase.DLL abort+0x31
mongod.exe ...\src\mongo\util\assert_util.cpp(129) mongo::invariantOKFailed+0x228
mongod.exe ...\src\mongo\db\storage\wiredtiger\wiredtiger_kv_engine.cpp(352) mongo::WiredTigerKVEngine::WiredTigerCheckpointThread::run+0x661
mongod.exe ...\src\mongo\util\background.cpp(153) mongo::BackgroundJob::jobBody+0x131
mongod.exe c:\program files (x86)\microsoft visual studio 14.0\vc\include\thr\xthread(247) std::_LaunchPad<std::unique_ptr<std::tuple<<lambda_8929d5e2502e4de5883694c1a7a329eb> >,std::default_delete<std::tuple<<lambda_8929d5e2502e4de5883694c1a7a329eb> > > > >::_Run+0x77
mongod.exe c:\program files (x86)\microsoft visual studio 14.0\vc\include\thr\xthread(210) std::_Pad::_Call_func+0x9
ucrtbase.DLL o__realloc_base+0x60
KERNEL32.DLL BaseThreadInitThunk+0x22
2021-07-23T19:05:33.022+0530 I CONTROL [WTCheckpointThread] writing minidump diagnostic file C:\Program Files\MongoDB\Server\4.2021-07-23T13-35-33.mdmp
2021-07-23T19:13:01.047+0530 I NETWORK [listener] connection accepted from PrimaryHost:51006 #182621 (15 connections now open)
|
|
Hi madhabchpal,
We've successfully reproduced this issue on 3.2.4. However, we are unable to reproduce the same issue on the latest version of MongoDB 3.2.20. Therefore, we would strongly recommend that you upgrade to latest version of MongoDB 3.2, as we expect that this issue is likely resolved by one of the fixes included sine 3.2.4 was released. Since we're unable to reproduce this issue in more recent versions, I've gone ahead and closed the ticket.
Please let us know if you encounter the issue after upgrading and we'll continue to investigate.
Kind regards,
Kelsey
|
|
We're going to try to reproduce your error to see what the problem might be. Certainly there is a performance cost to turning on operationProfiling, so I recommend turning it on only when you are actively interested in the data that the profiler produces. However, there ought to be no operational problems like the one you experienced here.
|
|
Thank you Eric for your suggestions.
Basically, setting the operationProfiling in mongod.conf to mode: off in all the replica set members, successfully connected the replica set member which was getting signal 22. I had not to drop admin.system.profile collection at all.
Now, I am confused if it is good idea to keep operationProfiling off in production environment? Please suggest.
|