[SERVER-24155] can't start mongod: aborting after invariant() failure Created: 16/May/16 Updated: 22/Apr/19 Resolved: 16/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.2.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | alfredopacino | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Hi, I get this error trying to start my mongo deamon: NOTE I don't see any sizeStorer.wt in my DB folder. 2016-05-16T17:23:06.521+0200 I CONTROL [main] Hotfix KB2731284 or later update is not installed, will zero-out data files } ***aborting after invariant() failure |
| Comments |
| Comment by Michael Brenden [ 22/Apr/19 ] |
|
Check the obvious – file limits ulimit -n Default file limit of 1,024 is probably nowhere near enough. |
| Comment by Kelsey Schubert [ 16/May/16 ] |
|
Hi alfredopacino, Thanks for the quick response. Journaling is enabled by default. If your $dbpath was modified by git operations, this would most likely explain the behavior you are observing. Please note that data files in the $dbpath should only be committed when the mongod process is shut down or after executing db.fsyncLock(), otherwise the files committed may be in an inconsistent state. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. Questions about using version control on your $dbpath would involve more discussion would be best posted on the mongodb-users group. Kind regards, |
| Comment by alfredopacino [ 16/May/16 ] |
|
First of all I'm relatively new to mongodb Today (before the I noticed the mongod error) I worked on git (removing and add directories and files from my repos, so I operated on the db directory c:\myproject\data through git). Nothing more. I don't think it's related to this issue... although it's the only thing I've done. |
| Comment by Kelsey Schubert [ 16/May/16 ] |
|
Hi alfredopacino, Thanks for reporting this issue. To get a better understanding of what is going on, please answer the following questions:
Thank you, |