MongoDB.service failed with result exit-code

Question

I can't start mongoDB with the command "sudo systemctl start mongod".

I'm getting the following message :

● mongod.service - MongoDB Database Server
   Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-02-19 22:39:00 CET; 2s ago
     Docs: https://docs.mongodb.org/manual
  Process: 29368 ExecStart=/usr/bin/mongod --config /etc/mongod.conf (code=exited, status=14)
 Main PID: 29368 (code=exited, status=14)

Feb 19 22:39:00 pop-os systemd[1]: Started MongoDB Database Server.
Feb 19 22:39:00 pop-os systemd[1]: mongod.service: Main process exited, code=exited, status=14/n/a
Feb 19 22:39:00 pop-os systemd[1]: mongod.service: Failed with result 'exit-code'.

I've already reinstalled mongodb and I having the same problem. I don't know where the error came from if you can help me. Thank you.

Its always good practice is to check the logs first and find out the actual cause. Here is the log location `/var/log/mongodb/` — Muhammad Tariq, Mar 05 '21 at 05:50

score 97 · Answer 1 · edited Feb 02 '22 at 10:23

97

Just do those two commands for temporary solution:

sudo rm -rf /tmp/mongodb-27017.sock
sudo service mongod start

For details:

That shall be fault due to user permissions in .sock file, You may have to change the owner to monogdb user.

sudo chown -R mongodb:mongodb /var/lib/mongodb
sudo chown mongodb:mongodb /tmp/mongodb-27017.sock

For more details visit Documentation for installation

edited Feb 02 '22 at 10:23

alper

2,299
4
36
73

answered Dec 28 '20 at 20:32

Mohamed Sabry

1,513
7
8

1

In case, you are getting a permission error after running chown commands, then after running each command, run "sudo !!" after each command. – Muhammad Bilal Jan 31 '22 at 15:53
Best solution, work on Ubuntu 19.04. – Willy satrio nugroho May 31 '22 at 08:05

score 24 · Answer 2 · answered Nov 23 '20 at 07:19

24

I had the same problem in Manjaro and these commands solved it:

chown -R mongodb:mongodb /var/lib/mongodb
chown mongodb:mongodb /tmp/mongodb-27017.sock

answered Nov 23 '20 at 07:19

HosseinNedaee

380
3
6

score 15 · Answer 3 · answered Sep 18 '20 at 10:08

15

This worked for me and I don't reinstall MongoDB. I have created manually

sudo mkdir /var/lib/mongodb
sudo mkdir /var/log/mongodb

and changed owner for both

sudo chown -R mongodb:mongodb /var/lib/mongodb
sudo chown -R mongodb:mongodb /var/log/mongodb

answered Sep 18 '20 at 10:08

MD RAKIBUL ISLAM RAKIB

151
1
4

Every other solution didn't work, except for this. I'm running Elementary OS – paulobunga Jan 28 '21 at 06:54
This work, thank you! – Wing Shum Oct 19 '21 at 16:05
Thank you it worked. I tried everything, changing permission, reinstalling, creating and changing /data/db permissions and a lot of other things, none worked except for this – heethjain21 Nov 26 '21 at 04:45
Out of curiosity, what bug does this solution fix? It seems like this shouldn't be necessary but it worked for me – Matthew Lin Jan 10 '22 at 02:55

score 7 · Answer 4 · answered Aug 25 '21 at 13:26

7

These two commands solve the problem for me(Linux Mint 20.2).

sudo chown -R mongodb:mongodb /var/lib/mongodb
sudo chown mongodb:mongodb /tmp/mongodb-27017.sock

answered Aug 25 '21 at 13:26

Mr. Kabir

119
1
2

2

This worked for ubuntu 20.04 – Viraj Jan 15 '22 at 16:29
This worked for me too on ubuntu 20.04...but WHY did this work @Mr.Kabir? – PA-GW Jan 23 '22 at 21:59
i can confirm that works in ubuntu 20.04 – Cipto HD Mar 04 '22 at 04:02
Worked for me on Ubuntu 20.04 as well. Thanks! – don_jon Apr 09 '22 at 00:05

score 3 · Answer 5 · answered Jan 01 '22 at 22:22

This will worked for you and don't reinstall MongoDB.

sudo mkdir /var/lib/mongodb
sudo mkdir /var/log/mongodb

then run these commands

sudo chown -R mongodb:mongodb /var/lib/mongodb
sudo chown -R mongodb:mongodb /var/log/mongodb

start mongod service

sudo service mongod start

mongod.service will be active

sudo service mongod status

score 3 · Answer 6 · answered Mar 28 '22 at 08:42

This error happend to me because of the ownship of the .sock file just try these two command

chown -R mongodb:mongodb /var/lib/mongodb
chown mongodb:mongodb /tmp/mongodb-27017.sock

now restart the mongo server-

sudo systemctl start mongod

now you can check the status of mongo server with the following command -

sudo systemctl status mongod

score 0 · Answer 7 · answered Aug 31 '21 at 07:45

0

These 3 steps solved my problem:

sudo chown -R mongodb:mongodb /var/lib/mongodb
sudo chown -R mongodb:mongodb /var/log/mongodb
sudo chown mongodb:mongodb /tmp/mongodb-27017.sock

answered Aug 31 '21 at 07:45

Sudarshan

1
2
2

score 0 · Answer 8 · answered Dec 10 '21 at 10:18

0

sudo mongod --dbpath /var/lib/mongodb/ --journal

answered Dec 10 '21 at 10:18

UmeshRauthela

9
1

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Dec 10 '21 at 16:22

MongoDB.service failed with result exit-code

8 Answers8

Linked