4

在我们的 vps 关闭并启动它后，mongod 服务没有自动启动，我们无法启动它service mongod start，文件/var/log/mongo/mongod.log包含以下日志：

  ***** SERVER RESTARTED *****


Thu Oct 11 13:51:18 
Thu Oct 11 13:51:18 warning: 32-bit servers don't have journaling enabled by default. Please use --journal if you want durability.
Thu Oct 11 13:51:18 
Thu Oct 11 13:51:18 [initandlisten] MongoDB starting : pid=3821 port=27017 dbpath=/var/lib/mongo 32-bit host=server2.paransa.org
Thu Oct 11 13:51:18 [initandlisten] 
Thu Oct 11 13:51:18 [initandlisten] ** NOTE: when using MongoDB 32 bit, you are limited to about 2 gigabytes of data
Thu Oct 11 13:51:18 [initandlisten] **       see http://blog.mongodb.org/post/137788967/32-bit-limitations
Thu Oct 11 13:51:18 [initandlisten] **       with --journal, the limit is lower
Thu Oct 11 13:51:18 [initandlisten] 
Thu Oct 11 13:51:18 [initandlisten] ** WARNING: You are running in OpenVZ. This is known to be broken!!!
Thu Oct 11 13:51:18 [initandlisten] 
Thu Oct 11 13:51:18 [initandlisten] db version v2.2.0, pdfile version 4.5
Thu Oct 11 13:51:18 [initandlisten] git version: f5e83eae9cfbec7fb7a071321928f00d1b0c5207
Thu Oct 11 13:51:18 [initandlisten] build info: Linux domU-12-31-39-01-70-B4 2.6.21.7-2.fc8xen #1 SMP Fri Feb 15 12:39:36 EST 2008 i686 BOOST_LIB_VERSION=1_49
Thu Oct 11 13:51:18 [initandlisten] options: { config: "/etc/mongod.conf", dbpath: "/var/lib/mongo", fork: "true", logappend: "true", logpath: "/var/log/mongo/mongod.log", pidfilepath: "/var/run/mongodb/mongod.pid" }
Thu Oct 11 13:51:18 [initandlisten] couldn't open /var/lib/mongo/mydb_main.ns errno:13 Permission denied
Thu Oct 11 13:51:18 [initandlisten] error couldn't open file /var/lib/mongo/mydb_main.ns terminating
Thu Oct 11 13:51:18 dbexit: 
Thu Oct 11 13:51:18 [initandlisten] shutdown: going to close listening sockets...
Thu Oct 11 13:51:18 [initandlisten] shutdown: going to flush diaglog...
Thu Oct 11 13:51:18 [initandlisten] shutdown: going to close sockets...
Thu Oct 11 13:51:18 [initandlisten] shutdown: waiting for fs preallocator...
Thu Oct 11 13:51:18 [initandlisten] shutdown: closing all files...
Thu Oct 11 13:51:18 [initandlisten] closeAllFiles() finished
Thu Oct 11 13:51:18 [initandlisten] shutdown: removing fs lock...
Thu Oct 11 13:51:18 dbexit: really exiting now

如您所见，日志显示 mongo 服务器无法打开 *.ns 文件导致权限湖

但是如果我通过以下命令手动运行服务器：

mongod --dbpath=/var/lib/mongo -f /etc/mongod.conf

似乎一切都很好，关于日志文件：

***** SERVER RESTARTED *****


Thu Oct 11 14:02:06 
Thu Oct 11 14:02:06 warning: 32-bit servers don't have journaling enabled by default. Please use --journal if you want durability.
Thu Oct 11 14:02:06 
Thu Oct 11 14:02:06 [initandlisten] MongoDB starting : pid=4090 port=27017 dbpath=/var/lib/mongo 32-bit host=server2.paransa.org
Thu Oct 11 14:02:06 [initandlisten] 
Thu Oct 11 14:02:06 [initandlisten] ** NOTE: when using MongoDB 32 bit, you are limited to about 2 gigabytes of data
Thu Oct 11 14:02:06 [initandlisten] **       see http://blog.mongodb.org/post/137788967/32-bit-limitations
Thu Oct 11 14:02:06 [initandlisten] **       with --journal, the limit is lower
Thu Oct 11 14:02:06 [initandlisten] 
Thu Oct 11 14:02:06 [initandlisten] ** WARNING: You are running in OpenVZ. This is known to be broken!!!
Thu Oct 11 14:02:06 [initandlisten] 
Thu Oct 11 14:02:06 [initandlisten] db version v2.2.0, pdfile version 4.5
Thu Oct 11 14:02:06 [initandlisten] git version: f5e83eae9cfbec7fb7a071321928f00d1b0c5207
Thu Oct 11 14:02:06 [initandlisten] build info: Linux domU-12-31-39-01-70-B4 2.6.21.7-2.fc8xen #1 SMP Fri Feb 15 12:39:36 EST 2008 i686 BOOST_LIB_VERSION=1_49
Thu Oct 11 14:02:06 [initandlisten] options: { config: "/etc/mongod.conf", dbpath: "/var/lib/mongo", fork: "true", logappend: "true", logpath: "/var/log/mongo/mongod.log", pidfilepath: "/var/run/mongodb/mongod.pid" }
Thu Oct 11 14:02:07 [websvr] admin web console waiting for connections on port 28017
Thu Oct 11 14:02:07 [initandlisten] waiting for connections on port 27017

并使用 --repair arg 没有帮助（可能是因为它可以手动启动mongod --dbpath=/var/lib/mongo -f /etc/mongod.conf并将 --repair arg 添加到命令中，记录一切都很好！...）

有什么建议吗？

4

5 回答 5

16

这是一个权限问题，当您通过服务启动时，您正在以 mongod（或 mongodb 等）用户身份运行，而当您使用 sudo 或以 root 身份调用时，您可能以 root 身份运行（您在上面的评论中确认了这一点）。您需要修复该文件夹中所有文件的权限，并且永远不要以 root 身份启动服务。

要根据您发布的内容修复文件，假设您的相关用户是 mongodb 并且该组是 mongodb，您将使用 sudo（或作为 root）执行以下操作 - 替换您系统的相应用户：

chown -R mongodb:mongodb /var/lib/mongo
chown -R mongodb:mongodb /var/run/mongodb
chown mongodb:mongodb /var/log/mongo/mongod.log

修复这些文件夹的权限后，您应该能够再次通过服务启动。注意：如果你发布ls -al /var/lib/mongothen 我可以给你你需要运行的确切命令

于 2012-10-12T10:17:02.357 回答
4 
sudo rm /data/db/mongod.lock
sudo mongod --dbpath /data/db --repair
sudo mongod --dbpath /data/db
于 2013-07-26T07:07:24.187 回答
2

尝试在 CMD 中启动 mongod.exe 之前删除*.lock文件夹中的文件。"\data\db"

于 2012-10-12T12:16:02.557 回答
2 
Stop the MongoDB service

sudo service mongodb stop 删除 MongoDB 锁定文件

sudo rm /var/lib/mongodb/mongod.lock

Change ownership from root to the MongoDB path

sudo chown -R mongodb:mongodb /var/lib/mongodb/

Access the mongodb Shell   

 sudo mongod --dbpath=/var/lib/mongodb

Start the MongoDB service

sudo service mongodb start
Test the mongo application

mongo
于 2014-09-08T12:36:01.173 回答
1

rc.local您可以使用以下命令从 永远自动运行您的 mongodb ：

su pi -c 'sudo mongod --repairpath your_path'

并且不用担心意外关机。

于 2018-11-14T09:32:57.800 回答