[SERVER-43220] mongodb is not starting up Created: 06/Sep/19 Updated: 11/Nov/19 Resolved: 11/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sushil Rane | Assignee: | Carl Champain (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
service mongod start Starting mongod: 2019-09-06T18:44:47.720-0500 W CONTROL [main] Option: storage.mmapv1.journal.commitIntervalMs is deprecated. Please use storage.journal.commitIntervalMs instead. about to fork child process, waiting until server is ready for connections. forked process: 3209 ERROR: child process failed, exited with error number 100 [FAILED] |
| Comments |
| Comment by Carl Champain (Inactive) [ 11/Nov/19 ] |
|
Hi surane@adobe.com, We haven’t heard back from you for some time, so I’m going to mark this ticket as incomplete. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, |
| Comment by Carl Champain (Inactive) [ 09/Oct/19 ] |
|
Hi surane@adobe.com, Any updates on this issue? |
| Comment by Carl Champain (Inactive) [ 10/Sep/19 ] |
|
Hi surane@adobe.com, Thanks for the report.
The ideal resolution is to perform a clean resync from an unaffected node. You can also try mongod --repair. Importantly, 3.2 version of MongoDB is already end-of-lifed, you should upgrade to the latest 4.2.0 or 4.0.12. Regards, |