为什么得到错误mongod死了,但是锁定并且Linux上的日志文件的可用空间不足?

时间:2013-01-29 13:44:16

标签: linux mongodb journal

我在Linux CentOS服务器上安装了 mongo-10gen mongo-10gen-server

我按照Link的步骤进行了操作。

我已将 /etc/mongod.conf 配置为 -

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

我在 iptables 中为mongo设置了端口27017。 要启动mongo,我使用了命令 -

service mongod start and
mongo

它开始很好,但几天后我收到了错误 -

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

当我执行命令 -

service mongod status

它给出错误 -

mongod dead but subsys locked

请帮我解决 mongod dead但问题已锁定 期刊可用空间不足,终止的问题

7 个答案:

答案 0 :(得分:87)

您可以在运行mongod --config mongod.conf

时向配置文件中添加以下内容

对于MongoDB 3.x (最新版本)

storage:
   mmapv1:
      smallFiles: true

版本 2.6 +

storage:
   smallFiles: true

版本 2.4 及更少

smallfiles = true

然后执行mongod接受你的配置文件(这里它假设配置的位置是 /etc/mongodb.conf ):

mongod -f /etc/mongodb.conf

Documentation smallfiles 参数:

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.

答案 1 :(得分:53)

使用以下命令启动mongod实例

mongod --dbpath /data/db --smallfiles

答案 2 :(得分:11)

我正在关注http://docs.mongodb.org/manual/tutorial/install-mongodb-on-ubuntu/

的官方指南

使用后

$sudo service mongod start

我通过查看此日志来验证MongoDB是否已成功启动:

/var/log/mongodb/mongod.log

这是我发现的问题:

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

解决方案:

在文件/etc/mongod.conf的末尾,我添加了这一行:

smallfiles = true

之后,我重启了mongod服务:

$sudo service mongod restart

然后,当我去查看日志时,我意识到一切都很完美,问题得到解决:

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

答案 3 :(得分:1)

对于有这个问题的人,尽管有足够的空间来创建日记文件。

我的问题:我有足够的空间来创建日志文件。 Mongo给了我一个连接失败的问题。我使用kill命令来杀死mongod进程,这反过来给了我subsys问题。这对我有用:

转到/var/lock/subsys并删除文件mongod

现在service mongod stop然后service mongod start

现在开始使用mongo shell,一切似乎都运行良好。

答案 4 :(得分:0)

第一

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

然后

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

答案 5 :(得分:0)

只是一张纸条,这对我很有帮助。虽然没有与mongo相关的技术问题。只是系统的空间不足。清除系统的缓存对我来说很明显,mongo恢复运行。

yum clean all

答案 6 :(得分:0)

问题背景:我将数据库服务器从t2.micro升级到了更大的实例,而没有停止数据库服务。作为回报,该文件创建了此锁定文件并抛出此错误,   mongod已死但子系统已锁定 此后,我无法使用mongo shell。

如果您有足够的磁盘空间。然后按照以下步骤操作,

1. sudo mongod (如果您发现以下失败原因)

Failed to unlink socket file /tmp/mongodb-27017.sock Operation not permitted)
  1. 转到 / tmp / 目录

  2. 删除 mongodb-27017.sock 文件

  3. 使用 sudo service mongod restart

  4. 重新启动mongod