Home / ubuntu / Questions / 884541
Accepted
Mina Michael
Asked: 2017-02-18 16:21:12 +0800 CST

Can't start mongodb service

  • 772

Following this guide to install mongodb but mongo just doesn't want to start.

When running sudo systemctl status mongodb It just shows Active: failed (Result: exit-code). There's no useful output in this. How do I find out why is it not starting?

Edit:

output of ls -al /etc/systemd/system/mongodb.service

-rw-r--r-- 1 root root 220 Feb 17 23:59 /etc/systemd/system/mongodb.service

output of cat /etc/systemd/system/mongodb.service

[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

output of mongod

2017-02-18T10:19:55.072+0200 I CONTROL  [initandlisten] MongoDB starting : pid=6617 port=27017 dbpath=/data/db 64-bit host=sherrie-HP-Pavilion-x360-m3-Convertible
2017-02-18T10:19:55.072+0200 I CONTROL  [initandlisten] db version v3.2.12
2017-02-18T10:19:55.072+0200 I CONTROL  [initandlisten] git version: ef3e1bc78e997f0d9f22f45aeb1d8e3b6ac14a14
2017-02-18T10:19:55.072+0200 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
2017-02-18T10:19:55.072+0200 I CONTROL  [initandlisten] allocator: tcmalloc
2017-02-18T10:19:55.072+0200 I CONTROL  [initandlisten] modules: none
2017-02-18T10:19:55.072+0200 I CONTROL  [initandlisten] build environment:
2017-02-18T10:19:55.072+0200 I CONTROL  [initandlisten]     distmod: ubuntu1604
2017-02-18T10:19:55.072+0200 I CONTROL  [initandlisten]     distarch: x86_64
2017-02-18T10:19:55.072+0200 I CONTROL  [initandlisten]     target_arch: x86_64
2017-02-18T10:19:55.072+0200 I CONTROL  [initandlisten] options: {}
2017-02-18T10:19:55.137+0200 I -        [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2017-02-18T10:19:55.155+0200 I STORAGE  [initandlisten] exception in initAndListen: 98 Unable to create/open lock file: /data/db/mongod.lock errno:13 Permission denied Is a mongod instance already running?, terminating
2017-02-18T10:19:55.155+0200 I CONTROL  [initandlisten] dbexit:  rc: 100
mongodb

4 Answers

  1. Best Answer

    Just a simple reinstall worked.

    sudo apt purge mongodb-org*
sudo rm -r /var/log/mongodb
sudo rm -r /var/lib/mongodb
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv EA312927
echo "deb http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.2 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-3.2.list
sudo apt update
sudo apt-get install -y mongodb-org

    and double-check the config file:

    sudo nano /etc/systemd/system/mongodb.service

    paste 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

    finally

    sudo systemctl start mongodb
sudo systemctl enable mongodb

    also I think I changed the permissions of the log file to 777

    • 18

  2. This Worked for me.

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

    I am using Linux Mint 20.

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

sudo systemctl restart mongod
sudo systemctl status mongod

    these permission commands work for me on ubuntu 20.04

    • 4

  4. I run this command

    mongod --auth --fork

    because I had created admin user in admin DB before and then ran in this problem.

    • 0