MongoDB loads but breaks, returning status=14

Question

So im trying to setup Mongodb on Ubuntu 16.04 but im running into trouble.

when running :

sudo systemctl status mongodb

I get the following:

 mongodb.service - High-performance, schema-free document-oriented database
   Loaded: loaded (/etc/systemd/system/mongodb.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2016-09-10 14:02:22 CEST; 14s ago
     Docs: https://docs.mongodb.org/manual
  Process: 8724 ExecStart=/usr/bin/mongod --quiet --config /etc/mongod.conf (code=exited, status=14)
 Main PID: 8724 (code=exited, status=14)

According to the mongo-docs, status=14 is:

"Returned by MongoDB applications which encounter an unrecoverable error, an uncaught exception or uncaught signal. The system exits without performing a clean shut down."

I doesnt really point me in any particular direction.

My /etc/systemd/system/mongodb.service looks like this:

[Unit]
Description=High-performance, schema-free document-oriented database
After=network.target

[Service]
User=mongodb
ExecStart=/usr/bin/mongod --quiet --config /etc/mongod.conf

[Install]
WantedBy=multi-user.target

Any thought on what may be the cause of this?

Thank you

Hey Adam, sorry for not getting back here. I did solve the problem by reinstalling mongo. Thank you though. — user2915962, Sep 17 '16 at 14:04

score 252 · Answer 1 · edited Feb 10 '22 at 08:14

252

After googling around for a while. I found that that is because the permission settings on /var/lib/mongodb and /tmp/mongodb-27017.lock are wrong. You will have to change the owner to monogdb user

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

then

sudo service mongod restart

edited Feb 10 '22 at 08:14

Zanna

70,465

answered Dec 21 '18 at 07:08

xingliang

2,521
1
7
3

22

+1 for finding the undocumented chown mongodb:mongodb /tmp/mongodb-27017.sock... – Romeo Sierra May 24 '19 at 05:53
2

+1 for chown -R mongodb:mongodb /var/lib/mongodb – luongnv89 Aug 02 '19 at 15:20
4

I have lost yesterday just because of it. You should have good googling skills :) – Giorgi Gvimradze Aug 03 '19 at 08:14
Hi
I did change the permissions as above but still I'm unable to create a replica set which exits with error 14.Any ideas?

Here is the link that I'm using https://www.mongodb.com/blog/post/mongodb-change-streams-with-python
– Dhruv Marwha Jan 20 '20 at 05:49
1

This resolved my issue.. Thanks a lot :) – Dinesh Suthar Jun 02 '20 at 07:42
This answer literally saved my day. Thanks. – Ken Bekov Aug 10 '20 at 14:40
I have to do this EVERYTIME I want to start mongo...sucks, why??? – Michael Paccione Dec 29 '20 at 00:54
This worked perfectly! – Rohit Parte Jan 18 '21 at 15:39
It saved my day – Kasun Hasanga Mar 29 '21 at 01:23
I had to use your solution. Thanks. I report I created the problem myself by trying to run the service from the command line as root as: /usr/bin/mongod --config /etc/mongod.conf. Like that file permission you mention were mangled and set to root. – Nicola Mingotti Jun 25 '21 at 13:24
chown -R mongodb:mongodb /var/lib/mongodb did it for me , you are a hero – llermaly Jan 03 '22 at 02:36
It works for me after googling for 2 days. – MD Jahid Hasan Oct 09 '22 at 07:40
it's solved my problem on production, thank you – yussan Nov 25 '22 at 02:02
Resolved my issue thank you so much. – Neeraj Kumar Dec 22 '22 at 05:49
You are the messiah!! – Efrain Sanjay Adhikary Sep 27 '23 at 21:32
You saved me !!! – c3cris Oct 04 '23 at 00:47

Just applied that for me :

sudo chown mongodb:mongodb /tmp/mongodb-27017.sock
sudo systemctl restart mongod
sudo systemctl status mongod

Status was anew good after.

– Vifier Lockla Oct 22 '23 at 16:09

score 14 · Answer 2 · edited May 12 '20 at 15:14

14

By using this my error was gone:

Go to the TMP directory: cd /tmp
Check if you have the mongodb sock file: ls *.sock
Change the user:group permission: chown mongodb:mongodb <YOUR_SOCK>
Start MongoDB: sudo service mongod start
Check the MongoDB status: sudo service mongod status

edited May 12 '20 at 15:14

VidathD

2,704

answered May 12 '20 at 05:34

Avinash Buddana

141
1
3

in tmp i have no .sock files. What possibly can go wrong? – Giorgi Gvimradze Aug 14 '20 at 10:22
when i try to do it, it says operation not permitted, any ideas? – Yanis Dec 17 '21 at 19:37

score 13 · Answer 3 · answered Apr 09 '21 at 08:03

13

deleting the mongod sock file solved the issue for me sudo rm -rf /tmp/mongodb-27017.sock then start again sudo systemctl start mongod

answered Apr 09 '21 at 08:03

Shiroshan

131

score 5 · Answer 4 · edited Sep 22 '20 at 23:03

5

Check for both mentioned directories If they don't exist, use the following commands:

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

Clear the socket with the following command:

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

Restart and check the status of the service:

sudo service mongod restart

edited Sep 22 '20 at 23:03

Kevin Bowen

19,615
55
79
83

answered Aug 05 '20 at 16:26

Shashank Saxena

151

Just a small correction in response to your valuable answer in step 2 we need to add sudo before chown....... – Pranjal Gupta Mar 14 '21 at 09:13

score 3 · Answer 5 · answered Feb 01 '20 at 09:58

3

i tried this and it worked :

sudo nano /etc/mongod.conf

comment the "bind ip" line.

sudo mongod --auth --port 27017 --dbpath /data/db

then i ran

sudo service mongod restart

answered Feb 01 '20 at 09:58

Mohamed Belkamel

131

sezanzeb · Answer 6 · 2020-10-11T18:46:48.317

I also got status 14 at some point, but it was not because of my .lock files.

Looks like everything in your dbPath (in my case /data/mongodb) should belong to mongodb. In my case, two files and files in the journal folder were owned by root, possibly because I have run the mongod command with sudo instead of the mongodb user (as configured in mongod.service).

sudo chown mongodb:mongodb /data/mongodb/ -R

In order to find my problem, it helped to set the verbosity to 5 in /etc/mongod.conf:

systemLog:
  verbosity: 5

and run tail /var/log/mongodb/mongodb.log -n 100 after sudo systemctl start mongod

For this to work, mongod.conf needs to be loaded by mongod. mongod.service does that with the --config parameter.

Make sure to remove the high verbosity when your mongodb works again, because that logfile can grow very large.

score 1 · Answer 7 · answered Sep 27 '20 at 11:07

for beginners only if you are trying the following and getting errors :

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

then try checking the status

  sudo systemctl status mongod

it will show active ..

score 0 · Answer 8 · edited Oct 03 '22 at 07:55

0

Only in case of a fresh install: If /var/lib/mongodb is corrupt, rming it and reinstalling mongodb will work.

For a database with pre-existing data try:

mongod --repair --dbpath /var/lib/mongodb

edited Oct 03 '22 at 07:55

Brandon

3

answered Dec 14 '19 at 16:16

OverCoder

490
4
21

score 0 · Answer 9 · answered Jan 10 '21 at 07:00

0

This error occurred for me just because the disk space was full. And solved after deleting some unused files.

answered Jan 10 '21 at 07:00

Amin Shojaei

145

score 0 · Answer 10 · answered Mar 29 '21 at 16:00

0

In my case, it was because of an incomplete repair operation, in which case I had to run mongod --repair --dbpath /var/lib/mongodb.

answered Mar 29 '21 at 16:00

The Tablet

11

MongoDB loads but breaks, returning status=14

10 Answers10

Linked