
OPERATIONAL DEFECT DATABASE
...

...
Both mongos and mongod fail to cleanup their distributed lock ping documents at shutdown. 2016-02-06T00:49:11.259+0000 I CONTROL [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends 2016-02-06T00:49:11.262+0000 D SHARDING [signalProcessingThread] CatalogManagerReplicaSet::shutDown() called. 2016-02-06T00:49:11.262+0000 W SHARDING [signalProcessingThread] error encountered while cleaning up distributed ping entry for ip-10-159-168-74:20015:1454719718:-2097586284 :: caused by :: ShutdownInProgress: Shutdown in progress
manan@indeed.com commented on Fri, 13 Oct 2017 20:50:36 +0000: Ok, since this keep on occurring, I think we'll need to investigate on our end as to why is this process getting killed after a fixed amount of time. Will update if I find anything worth mentioning here. Thank you for your time. renctan commented on Fri, 13 Oct 2017 20:31:23 +0000: manan@indeed.com, would you clarify what you meant by crashing? The logs say that the mongos process exited with a return code of zero (normal terminate). And it also says that it got signal 2, which comes from somewhere external, so someone/something killed the mongos process. manan@indeed.com commented on Fri, 13 Oct 2017 18:55:38 +0000: Any update on this issue? I'm facing a similar error for the mongos instance that keeps on crashing due to the following error: (My mongo version is 3.2.12) 2017-10-13T13:27:49.031-0500 I CONTROL [signalProcessingThread] got signal 2 (Interrupt), will terminate after current cmd ends 2017-10-13T13:27:49.032-0500 W SHARDING [signalProcessingThread] error encountered while cleaning up distributed ping entry for my-host:37017:1507919190:-1474045303 :: caused by :: ShutdownInProgress: Shutdown in progress 2017-10-13T13:27:49.032-0500 I SHARDING [signalProcessingThread] dbexit: rc:0 renctan commented on Wed, 10 Feb 2016 19:45:56 +0000: Note: ping cleanup not essential to correctness and does not speed up lock take over. It's only purpose is to remove clutter in the config.lockpings collection.
Click on a version to see all relevant bugs
MongoDB Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.