Why make the mongod error dead, but subsys is locked and there is not enough free space for log files in Linux?

Question

I installed mongo-10gen mongo-10gen-server on a Linux CentOS server.

I followed the Link steps.

I configured /etc/mongod.conf as -

logpath=/var/log/mongo/mongod.log port=27017 dbpath=/var/lib/mongo 

I set port 27017 for mongo in iptables . To run mongo, I used the commands -

 service mongod start and mongo 

It started well, but after a few days I get an error message -

 Tue Jan 29 08:41:54 [initandlisten] ERROR: Insufficient free space for journal files Tue Jan 29 08:41:54 [initandlisten] Please make at least 3379MB available in /var/lib/mongo/journal or use --smallfiles Tue Jan 29 08:41:54 [initandlisten] Tue Jan 29 08:41:54 [initandlisten] exception in initAndListen: 15926 Insufficient free space for journals, terminating Tue Jan 29 08:41:54 dbexit: Tue Jan 29 08:41:54 [initandlisten] shutdown: going to close listening sockets... Tue Jan 29 08:41:54 [initandlisten] shutdown: going to flush diaglog... Tue Jan 29 08:41:54 [initandlisten] shutdown: going to close sockets... Tue Jan 29 08:41:54 [initandlisten] shutdown: waiting for fs preallocator... Tue Jan 29 08:41:54 [initandlisten] shutdown: lock for final commit... Tue Jan 29 08:41:54 [initandlisten] shutdown: final commit... Tue Jan 29 08:41:54 [initandlisten] shutdown: closing all files... Tue Jan 29 08:41:54 [initandlisten] closeAllFiles() finished Tue Jan 29 08:41:54 [initandlisten] journalCleanup... Tue Jan 29 08:41:54 [initandlisten] removeJournalFiles Tue Jan 29 08:41:54 [initandlisten] shutdown: removing fs lock... Tue Jan 29 08:41:54 dbexit: really exiting now 

When I execute the command -

 service mongod status 

He gives an error -

 mongod dead but subsys locked 

Please help me solve the mongod dead problem , but subsys is locked and there is not enough free space for logs, completion

Answer 1

You can add the following to the configuration file that is provided when you run mongod --config mongod.conf

For MongoDB 3.x (latest version)

 storage: mmapv1: smallFiles: true 

For version 2.6 +

 storage: smallFiles: true 

For version 2.4 and less

 smallfiles = true 

Then just run mongod to accept your configuration file (here it assumes the configuration location is / etc / mongodb.conf):

 mongod -f /etc/mongodb.conf 

Documentation for the smallfiles parameter:

 Set to true to modify MongoDB to use a smaller default data file size. Specifically, smallfiles reduces the initial size for data files and limits them to 512 megabytes. The smallfiles setting also reduces the size of each journal files from 1 gigabyte to 128 megabytes. 

Answer 2

Launch the mongod instance using the following command

 mongod --dbpath /data/db --smallfiles 

Answer 3

I followed the official guide at http://docs.mongodb.org/manual/tutorial/install-mongodb-on-ubuntu/

After use

 $sudo service mongod start 

I went to check if MongoDB was successful by looking at this log:

 /var/log/mongodb/mongod.log 

This is the problem I found:

 2014-11-11T12:54:05.808-0500 [initandlisten] ERROR: Insufficient free space for journal files 2014-11-11T12:54:05.808-0500 [initandlisten] Please make at least 3379MB available in /var/lib/mongodb/journal or use --smallfiles 2014-11-11T12:54:05.808-0500 [initandlisten] 2014-11-11T12:54:05.808-0500 [initandlisten] exception in initAndListen: 15926 Insufficient free space for journals, terminating 2014-11-11T12:54:05.808-0500 [initandlisten] dbexit: 2014-11-11T12:54:05.808-0500 [initandlisten] shutdown: going to close listening sockets... 2014-11-11T12:54:05.808-0500 [initandlisten] shutdown: going to flush diaglog... 2014-11-11T12:54:05.808-0500 [initandlisten] shutdown: going to close sockets... 2014-11-11T12:54:05.808-0500 [initandlisten] shutdown: waiting for fs preallocator... 2014-11-11T12:54:05.808-0500 [initandlisten] shutdown: lock for final commit... 2014-11-11T12:54:05.808-0500 [initandlisten] shutdown: final commit... 2014-11-11T12:54:05.808-0500 [initandlisten] shutdown: closing all files... 2014-11-11T12:54:05.808-0500 [initandlisten] closeAllFiles() finished 2014-11-11T12:54:05.808-0500 [initandlisten] journalCleanup... 2014-11-11T12:54:05.808-0500 [initandlisten] removeJournalFiles 2014-11-11T12:54:05.814-0500 [initandlisten] shutdown: removing fs lock... 2014-11-11T12:54:05.814-0500 [initandlisten] dbexit: really exiting now 

Decision:

At the end of the /etc/mongod.conf file, I added this line:

 smallfiles = true 

After that, I restarted the mongod service:

 $sudo service mongod restart 

Then, when I went to view the magazine, I realized that everything was perfect and the problem was fixed:

 2014-11-11T22:32:20.544-0500 ***** SERVER RESTARTED ***** 2014-11-11T22:32:20.552-0500 [initandlisten] MongoDB starting : pid=5200 port=27017 dbpath=/var/lib/mongodb 64-bit host=jaimemontoya-VirtualBox 2014-11-11T22:32:20.552-0500 [initandlisten] db version v2.6.5 2014-11-11T22:32:20.552-0500 [initandlisten] git version: e99d4fcb4279c0279796f237aa92fe3b64560bf6 2014-11-11T22:32:20.552-0500 [initandlisten] build info: Linux build8.nj1.10gen.cc 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49 2014-11-11T22:32:20.552-0500 [initandlisten] allocator: tcmalloc 2014-11-11T22:32:20.552-0500 [initandlisten] options: { config: "/etc/mongod.conf", net: { bindIp: "127.0.0.1" }, storage: { dbPath: "/var/lib/mongodb", smallFiles: true }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongod.log" } } 2014-11-11T22:32:20.564-0500 [initandlisten] journal dir=/var/lib/mongodb/journal 2014-11-11T22:32:20.564-0500 [initandlisten] recover : no journal files present, no recovery needed 2014-11-11T22:32:20.738-0500 [initandlisten] waiting for connections on port 27017 2014-11-11T22:33:20.748-0500 [clientcursormon] mem (MB) res:36 virt:245 2014-11-11T22:33:20.748-0500 [clientcursormon] mapped (incl journal view):64 2014-11-11T22:33:20.748-0500 [clientcursormon] connections:0 

Answer 4

For everyone who has this problem, despite having enough space for the generated log file.

My problem: I had enough space for the generated log file. Mongo gave me an error message. I used the kill command to kill the mongod process, which in turn gave me a subah question. Here is what worked for me:

Go to /var/lock/subsys and delete the mongod file

now service mongod stop and then service mongod start

The mongo shell will start now, and everything is working fine.

Answer 5

the first

 cd /usr/local/src/mongo/bin/<br> 

then

 ./mongod --dbpath /usr/local/src/mongo/data/db/ --smallfiles