Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Have 3 mongo DB servers on 3.4.20 with replicaset in place we are seeing fatal assertion 28558 at src\mongo\db\storage\wiredtiger\wiredtiger_util.cpp 365. We got this product as part of BMC Remedy 9.1.0.4 SP2 How to fix this error! why is this error generated! Is there a stable product from Mongo which is compatible with Smart IT Remedy 2.00.001
sanjay2019 commented on Wed, 15 May 2019 21:47:38 +0000: There is no previous configuration to revert to. I am bit surprised the core functionality is choking on all the version of mongo implementation, and have seen on mongo community as well, so thought its a server support project - If not kindly propagate this issue to concerned group. There are no antivirus or no configuration changes since deployment except a tag as authorized is enabled Get Outlook for iOShttps://aka.ms/o0ukef> eric.sedor commented on Wed, 15 May 2019 20:32:33 +0000: This error usually indicates that another process is accessing files critical to mongod, which we strongly recommend against. This is not limited to antivirus software. Unfortunately our ability to diagnose this as a potential bug will be limited unless you have the ability to provide specific reproduction steps. Does this make sense? We recommend reverting to your earlier configuration if you are urgently concerned about the overall availability of your deployment. To set expectations: This SERVER project is for reporting and investigating bug reports and feature suggestions for the MongoDB core server. It is not the best place to obtain urgent support for production environments. sanjay2019 commented on Wed, 15 May 2019 20:04:07 +0000: Any update Eric! sanjay2019 commented on Wed, 15 May 2019 16:42:19 +0000: I confirm we are running 3.4.20 on all 3 MongoDB nodes. No antivirus software accessing WT file eric.sedor commented on Wed, 15 May 2019 16:21:09 +0000: sanjay2019, the issue seems similar to WT-3962 which was backported to 3.4.14. Can you confirm the impacted nodes are indeed running 3.4.20? Can you also confirm that no other processes (such as antivirus software) are accessing the WiredTiger.turtle file? sanjay2019 commented on Wed, 15 May 2019 13:22:54 +0000: Just now we saw another server in production having FATAL Assertion issue.. Let me know how to resolve before we have outage due to the product!!! sanjay2019 commented on Wed, 15 May 2019 12:34:02 +0000: Any update Eric? sanjay2019 commented on Tue, 14 May 2019 17:36:28 +0000: Here you go Eric - I appreciate for your quick response. Please find mongoDB_logs.txt attached for your references. eric.sedor commented on Tue, 14 May 2019 16:48:07 +0000: Hi sanjay2019, can you please provide the mongod log files preceding the fatal assertion? We'd like to see additional context about the error. sanjay2019 commented on Tue, 14 May 2019 15:47:41 +0000: Originally, BMC Package came with 3.4.2 Mongo for Smart IT 1.6, we upgraded smart it to 2.0.00.1 and mongo to 3.4.20 (BMC recommended to be on 3.4.9.x) - we went even higher. The issue persists in Production today! we are windows server 2012 64bit! Any recommendations to resolve would be great. Not workaround a fix! or a stable product which is compatible with BMC Smart IT 2.0.001
Can some one tell me how to fix