OPERATIONAL DEFECT DATABASE
...
...
BugZero found this defect 2714 days ago.
Mongodb is getting down while in the midnight may be due to load. But how to avoid this Todays error : Unable to read the storage engine metadata file: FileNotOpen: Failed to read metadata from /var/lib/mongo/storage.bson 2017-08-10T03:00:47.483+0100 I - [initandlisten] Fatal Assertion 28661 2017-08-10T03:00:47.483+0100 I - [initandlisten] ***aborting after fassert() failure 2017-08-10T03:00:47.501+0100 F - [initandlisten] Got signal: 6 (Aborted). YEsterday : 2017-08-09T03:00:42.850+0100 E STORAGE [initandlisten] Unable to read the storage engine metadata file: FileNotOpen: Failed to read metadata from /var/lib/mongo/storage.bson 2017-08-09T03:00:42.850+0100 I - [initandlisten] Fatal Assertion 28661 2017-08-09T03:00:42.850+0100 I - [initandlisten] ***aborting after fassert() failure 2017-08-09T03:00:42.858+0100 F - [initandlisten] Got signal: 6 (Aborted).
thomas.schubert commented on Mon, 28 Aug 2017 18:33:45 +0000: Hi gg.anands@gmail.com, We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, Thomas thomas.schubert commented on Thu, 17 Aug 2017 15:50:42 +0000: Hi gg.anands@gmail.com, We still need additional information to diagnose the problem. If this is still an issue for you, would you please provide the information Dmitry requested? Thank you, Thomas dmitry.agranat commented on Thu, 10 Aug 2017 08:33:07 +0000: Hi gg.anands@gmail.com, Can you please archive and attach the $dbpath/diagnostic.data directory? Also, if you could compress and attach the complete mongod log file that contains the crash that could be helpful. Thanks, Dima
