Ask Your Question
0

Unit mongod.service entered failed state

asked 2015-07-29 06:20:35 -0600

neelabhsingh gravatar image

updated 2015-07-29 10:08:05 -0600

smaffulli gravatar image

I am running devstack on vertual machine. Initially I set the size of virtual machine 14 GB. I have enabled ceilometer. It fill the all space available on my virtual machine. In resource allocation I am unable to fetch the meters in metrix select parameter. When I run the sudo service mongod status It is giving the following out put

[vagrant@localhost init.d]$ sudo service mongod status
Redirecting to /bin/systemctl status  mongod.service
mongod.service - High-performance, schema-free document-oriented database
   Loaded: loaded (/usr/lib/systemd/system/mongod.service; enabled)
   Active: failed (Result: exit-code) since Wed 2015-07-29 11:45:14 BST; 29min ago
  Process: 1790 ExecStart=/usr/bin/mongod $OPTIONS run (code=exited, status=1/FAILURE)

Jul 29 11:45:14 localhost.localdomain mongod[1790]: about to fork child process, waiting until server is ready for connections.
Jul 29 11:45:14 localhost.localdomain mongod[1790]: forked process: 1792
Jul 29 11:45:14 localhost.localdomain mongod[1790]: ERROR: child process failed, exited with error number 1
Jul 29 11:45:14 localhost.localdomain systemd[1]: mongod.service: control process exited, code=exited status=1
Jul 29 11:45:14 localhost.localdomain systemd[1]: Failed to start High-performance, schema-free document-oriented database.
Jul 29 11:45:14 localhost.localdomain systemd[1]: Unit mongod.service entered failed state.

When I ran the df -h. It gives the following output

[vagrant@localhost init.d]$ df -h
Filesystem           Size  Used Avail Use% Mounted on
/dev/mapper/cl-root   14G   14G   20K 100% /
devtmpfs             2.4G     0  2.4G   0% /dev
tmpfs                2.4G   80K  2.4G   1% /dev/shm
tmpfs                2.4G  8.6M  2.4G   1% /run
tmpfs                2.4G     0  2.4G   0% /sys/fs/cgroup
tmpfs                2.4G  4.0K  2.4G   1% /tmp
/dev/sda1            497M  129M  369M  26% /boot
none                 721G  108G  614G  15% /vagrant

I tried the this link how-to-clean-up-old-ceilometer-data still I am getting the following output

[vagrant@localhost init.d]$ mongo --eval "db.dropDatabase();"
MongoDB shell version: 2.6.9
connecting to: test
2015-07-29T12:21:16.425+0100 warning: Failed to connect to 127.0.0.1:27017, reason: errno:111 Connection refused
2015-07-29T12:21:16.426+0100 Error: couldn't connect to server 127.0.0.1:27017 (127.0.0.1), connection attempt failed at src/mongo/shell/mongo.js:146
exception: connect failed
[vagrant@localhost init.d]$ 
[vagrant@localhost init.d]$ mongo --eval "db.dropDatabase();"
MongoDB shell version: 2.6.9
connecting to: test
2015-07-29T12:21:16.425+0100 warning: Failed to connect to 127.0.0.1:27017, reason: errno:111 Connection refused
2015-07-29T12:21:16.426+0100 Error: couldn't connect to server 127.0.0.1:27017 (127.0.0.1), connection attempt failed at src/mongo/shell/mongo.js:146
exception: connect failed
[vagrant@localhost init.d]$
edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
0

answered 2015-07-31 04:42:48 -0600

Shaoman Zhang gravatar image

Maybe not enough disk space. Try to delete files under /var/lib/mongodb/, and restart mongod service.

edit flag offensive delete link more

Comments

Not enough free space might be the root cause. Try to clean the mongodb's dir as was mentioned before. Also, to avoid db growing you can try limit meters lifetime setting the 'time_to_live' option in ceilometer.conf.([databse] section)

yprokule gravatar imageyprokule ( 2015-08-03 02:45:34 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-07-29 06:20:35 -0600

Seen: 2,701 times

Last updated: Jul 31 '15