[SERVER-30585] MongoDB Error: Unable to read storage Engine Meta Data Created: 10/Aug/17 Updated: 20/Sep/17 Resolved: 28/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Anand Mohan | Assignee: | Kelsey Schubert |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | RF | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
RHEL 7.3 |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
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 ***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 ***aborting after fassert() failure 2017-08-09T03:00:42.858+0100 F - [initandlisten] Got signal: 6 (Aborted). |
| Comments |
| Comment by Kelsey Schubert [ 28/Aug/17 ] |
|
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, |
| Comment by Kelsey Schubert [ 17/Aug/17 ] |
|
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, |
| Comment by Dmitry Agranat [ 10/Aug/17 ] |
|
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, |