0

UPDATE: I solved the issue by changing the storage engine to wiredTiger. I did this by editing /etc/mongod.conf and adding "engine: wiredTiger" after "journal: enabled: true"

Everytime I start MongoDB, it runs for about 1 second before crashing with the following error:

Active: failed (Result: exit-code) since Thu 2020-03-12 09:47:17 EDT; 6s ago Docs: https://docs.mongodb.org/manual Process: 1931 ExecStart=/usr/bin/mongod --config /etc/mongod.conf (code=exited, status=100) Main PID: 1931 (code=exited, status=100) Mar 12 09:47:14 myServer systemd[1]: Started MongoDB Database Server. Mar 12 09:47:17 myServer systemd[1]: mongod.service: Main process exited, code=exited, status=100/n/a Mar 12 09:47:17 myServer systemd[1]: mongod.service: Failed with result 'exit-code'.

Also, in the logs file:

Cannot start server with an unknown storage engine: mmapv1

I've tried reinstalling MongoDB, giving the mongodb user ownership of /var/lib/mongodb, and removing the mongodb.lock file, to no avail.

Any suggestions?

  • 1
    You can submit and accept an answer to your own question instead of editing the question with the solution. – Bert Mar 12 at 14:29
0

I solved the issue by changing the storage engine to wiredTiger. I did this by editing /etc/mongod.conf and adding "engine: wiredTiger" after "journal: enabled: true"

|improve this answer|||||

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.