Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Mongodb error on starting

When i start mongo db it instantly crashes and goes back to the normal command line. I am on Mac runing the MEAN stack if that helps. Below is the error:

$sudo mongod

Sun Jun  1 21:01:01.728 [initandlisten] MongoDB starting : pid=47937 port=3000 dbpath=/usr/local/var/mongodb 64-bit host=NoHax4You
Sun Jun  1 21:01:01.728 [initandlisten] 
Sun Jun  1 21:01:01.729 [initandlisten] ** WARNING: soft rlimits too low. Number of files is 256, should be at least 1000
Sun Jun  1 21:01:01.729 [initandlisten] db version v2.4.9
Sun Jun  1 21:01:01.729 [initandlisten] git version: nogitversion
Sun Jun  1 21:01:01.729 [initandlisten] build info: Darwin minimavericks.local 13.0.0 Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64 x86_64 BOOST_LIB_VERSION=1_49
Sun Jun  1 21:01:01.729 [initandlisten] allocator: tcmalloc
Sun Jun  1 21:01:01.729 [initandlisten] options: { bind_ip: "127.0.0.1", config: "/usr/local/etc/mongod.conf", dbpath: "/usr/local/var/mongodb", logappend: "true", logpath: "/usr/local/var/log/mongodb/mongo.log", port: 3000 }
Sun Jun  1 21:01:01.729 [initandlisten] exception in initAndListen: 10310 Unable to lock file: /usr/local/var/mongodb/mongod.lock. Is a mongod instance already running?, terminating
Sun Jun  1 21:01:01.729 dbexit: 
Sun Jun  1 21:01:01.729 [initandlisten] shutdown: going to close listening sockets...
Sun Jun  1 21:01:01.729 [initandlisten] shutdown: going to flush diaglog...
Sun Jun  1 21:01:01.729 [initandlisten] shutdown: going to close sockets...
Sun Jun  1 21:01:01.729 [initandlisten] shutdown: waiting for fs preallocator...
Sun Jun  1 21:01:01.729 [initandlisten] shutdown: lock for final commit...
Sun Jun  1 21:01:01.729 [initandlisten] shutdown: final commit...
Sun Jun  1 21:01:01.729 [initandlisten] shutdown: closing all files...
Sun Jun  1 21:01:01.729 [initandlisten] closeAllFiles() finished
Sun Jun  1 21:01:01.729 dbexit: really exiting now

Thanks, Ewan

like image 433
React Dev Avatar asked Jun 01 '14 19:06

React Dev


1 Answers

First of all, look for other instances of mongod running on the system using the age-old command:

ps ax | grep mongod

If you see a line like -

98555   ??  S      4:40.89 mongod --dbpath /Volumes/ComputerName/data/db 
-PID-                      -name-          -------------path------------

then there is a mongod process running already. If so kill it and then start mongod again.

To kill a process with PID = 0000, in Unix like environment use -

kill -9 0000

If your console returns something like, -bash: kill: (98555) - Operation not permitted, use

sudo !! 

to repeat the command as super user. This should get you going.


PS: If you haven't stored any data in your db yet, delete /data and then create the /data/db directory again. Do a sudo mongod and it should work.

like image 142
displayName Avatar answered Sep 21 '22 13:09

displayName