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 193 · Answer 1 · edited Feb 02 '22 at 10:23

193

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,919
9
53
102

answered Dec 28 '20 at 20:32

Mohamed Sabry

2,585
1
8
13

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
It worked great for me on Ubuntu 22.04. Thank you very much. – Pereira Jul 22 '22 at 17:58
it worked great for me on Ubuntu 20.04.6 LTS. – George Imerlishvili Sep 01 '23 at 12:35

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

36

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

500
5
6

Minhaj98 · Answer 3 · 2022-07-12T04:20:51.847

27

I had the same problem, so I tried changing the permissions and some other commands I found online that messed up my MongoDB installation. Following are the commands that I tried from online and screwed up my installation:

$ sudo chown mongodb:mongodb /tmp/mongodb-27017.sock

$ sudo systemctl status mongod

$ sudo systemctl start mongodb

$ sudo systemctl unmask mongodb

After that, I reinstall mongodb by using following commands, which solved the issue:

$ sudo service mongod stop

$ sudo apt-get purge mongodb-org*

$ sudo rm -r /var/log/mongodb

$ sudo rm -r /var/lib/mongodb

$ sudo apt-get install -y mongodb-org

Now start the mongodb and check the status using following commands:

$ sudo systemctl start mongod

$ sudo systemctl status mongod

edited Jul 12 '22 at 04:20

answered Jul 12 '22 at 04:20

Minhaj98

376
3
7

1

Great!. This solves the problem but it removes old databases as well and everytime if we face problem for exit code , this might not work. But this time it worked – James Aug 06 '22 at 19:29
Don't forget the quotes around `sudo apt-get purge 'mongodb-org*'` – Anne van Rossum Aug 26 '22 at 09:09
1

This worked for me, I also had to remove some leftovers: `sudo rm /usr/bin/mongo*` which were conflicting from an earlier install. – Dave Dec 16 '22 at 09:06

score 26 · Answer 4 · answered Sep 18 '20 at 10:08

26

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

Rakibulinux

451
5
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
1

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 12 · Answer 5 · answered Aug 25 '21 at 13:26

12

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

695
8
9

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? – CodeConnoisseur 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 7 · 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 5 · Answer 7 · 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 4 · Answer 8 · answered Sep 28 '22 at 05:07

4

for me, this works

sudo systemctl stop mongod
sudo mongod --repair --dbpath /var/lib/mongodb
sudo chown -R mongodb:mongodb /var/lib/mongodb
sudo chown mongodb:mongodb /tmp/mongodb-27017.sock
sudo systemctl start mongod

answered Sep 28 '22 at 05:07

Syed Aman Ali

151
5

Thanks to @[https://stackoverflow.com/users/811240/mike](Mike), I was reminded of reading logs. For this answer, the situation is that: `Failed to unlink socket file`, "Operation not permitted"`. – Ryuujo Jun 07 '23 at 12:25

score 2 · Answer 9 · answered Dec 05 '22 at 15:45

It's weird that none of the other answers here mention to look in the log files. This should always be the first thing you do. On Ubuntu, this is located at /var/log/mongodb/mongod.log.

In my case, I was getting messages like the following:

{
   "t":{
      "$date":"2022-12-03T17:19:25.117+00:00"
   },
   "s":"F",
   "c":"CONTROL",
   "id":20574,
   "ctx":"main",
   "msg":"Error during global initialization",
   "attr":{
      "error":{
         "code":140,
         "codeName":"InvalidSSLConfiguration",
         "errmsg":"ssl client initialization problem for certificate: /etc/ssl/mongodb.pem :: caused by :: The provided SSL certificate is expired or not yet valid. notBefore 2022-08-22T21:15:57.000+00:00, notAfter 2022-11-20T21:15:56.000+00:00"
      }
   }
}

So, the solution was to update the SSL certificate, which had expired.

If you are using Let's Encrypt, here's a --post-hook script to do this automatically (change example.com to your domain):

#!/bin/bash
cat /etc/letsencrypt/live/example.com/{fullchain.pem,privkey.pem} | tee /etc/ssl/mongodb.pem 
chown mongodb:mongodb /etc/ssl/mongodb.pem
chmod 600 /etc/ssl/mongodb.pem

If the certificate already exists, you can also add this under [renewalparams] of /etc/letsencrypt/renewal/example.com.conf

post_hook = /root/path/to/script.sh

Or you can just do a one-liner instead of linking to an external script:

post_hook = cat /etc/letsencrypt/live/example.com/fullchain.pem /etc/letsencrypt/live/example.com/privkey.pem | sudo tee /etc/ssl/mongodb.pem && chown mongodb:mongodb /etc/ssl/mongodb.pem && chmod 600 /etc/ssl/mongodb.pem

This answer should be bumped up. In my case, after looking at the log, I saw that the error was the TCP port was in use by something else. I then ran "sudo lsof -i -P -n | grep LISTEN" to figure out who was the culprit (for me it was mongo running in a docker container). — Cosmo, Apr 14 '23 at 14:43

score 0 · Answer 10 · 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
1
2
2

score 0 · Answer 11 · 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

score 0 · Answer 12 · answered Dec 15 '22 at 12:14

I had the same issue on AWS EC2 ubuntu server. I eventually found out that this was due to lack of available space on the disk. I ran df -h to determine which partition is full, and compared it to my volume on AWS console (this guide helped).

I increased the available storage on the AWS volume, ran sudo reboot now and the issue was fixed

score 0 · Answer 13 · answered Aug 02 '23 at 08:50

0

Use this command:

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

then this command:

sudo chown mongodb:mongodb /tmp/mongodb-27017.sock

answered Aug 02 '23 at 08:50

ayush

1
1

MongoDB.service failed with result exit-code

13 Answers13

Linked