我们正在为 Amazon EC2 实例上的生产环境设置 MongoDB 服务器，但无法启动该服务。我关注了this设置文档。以下是我设置服务器的步骤:

在 /etc/yum.repos.d/mongodb-org-3.0.repo 中添加了以下内容

[mongodb-org-3.0]
name=MongoDB Repository
baseurl=http://repo.mongodb.org/yum/redhat/$releasever/mongodb-org/3.0/x86_64/
gpgcheck=0
enabled=1

并使用 sudo yum install -y mongodb-org-3.0.2

为数据、日志和日志创建了三个分区:

sudo mkdir /mongo
sudo mkdir /mongo/data
sudo mkdir /mongo/log
sudo mkdir /mongo/journal

为三个独立的分区创建文件系统:

sudo mkfs.ext4 /dev/xvdb
sudo mkfs.ext4 /dev/xvdc
sudo mkfs.ext4 /dev/xvdd

在 fstab 中创建用于重启的条目:

echo '/dev/xvdb /mongo/data ext4 defaults,auto,noatime,noexec 0 0
/dev/xvdc /mongo/journal ext4 defaults,auto,noatime,noexec 0 0
/dev/xvdd /mongo/log ext4 defaults,auto,noatime,noexec 0 0' | sudo tee -a /etc/fstab

并安装分区:

sudo mount /mongo/data
sudo mount /mongo/journal
sudo mount /mongo/log

给定权限并创建链接

sudo chown mongod:mongod /mongo/data /mongo/journal /mongo/log
sudo ln -s /mongo/journal /mongo/data/journal

配置 ulimit 和预读设置，如上面的文档链接中给出的。已验证的权限和分区:

[deployer@prod-mongo ~]$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda1      8.0G  1.3G  6.8G  16% /
devtmpfs        3.6G     0  3.6G   0% /dev
tmpfs           3.5G     0  3.5G   0% /dev/shm
tmpfs           3.5G   57M  3.4G   2% /run
tmpfs           3.5G     0  3.5G   0% /sys/fs/cgroup
/dev/xvdc       7.8G   36M  7.3G   1% /mongo/journal
/dev/xvdb       150G   51M  149G   1% /mongo/data
/dev/xvdd       3.9G   16M  3.6G   1% /mongo/log

权限:

[deployer@prod-mongo ~]$ ll /
total 32
lrwxrwxrwx.   1 root   root      7 Sep 29  2014 bin -> usr/bin
dr-xr-xr-x.   4 root   root   4096 Sep 29  2014 boot
drwxr-xr-x.  17 root   root   2860 May 11 12:11 dev
lrwxrwxrwx.   1 root   root      7 Sep 29  2014 lib -> usr/lib
lrwxrwxrwx.   1 root   root      9 Sep 29  2014 lib64 -> usr/lib64
drwxr-xr-x.   2 root   root      6 Jun 10  2014 mnt
drwxr-xr-x.   5 mongod mongod   41 May 11 05:06 mongo
drwxr-xr-x.  21 root   root    660 May 11 12:47 run
lrwxrwxrwx.   1 root   root      8 Sep 29  2014 sbin -> usr/sbin

在/mongo

[deployer@prod-mongo ~]$ ll /mongo/
total 12
drwxr-xr-x. 3 mongod mongod 4096 May 11 07:33 data
drwxr-xr-x. 3 mongod mongod 4096 May 11 07:31 journal
drwxr-xr-x. 3 mongod mongod 4096 May 11 08:58 log

更改/etc/mongodb.conf中的配置后

logpath=/mongo/log/mongod.log
dbpath=/mongo/data

当我这样做时:sudo service mongod start，我得到了这个错误:

Starting mongod (via systemctl):  Job for mongod.service failed. See 'systemctl status mongod.service' and 'journalctl -xn' for details.
                                                           [FAILED]

进一步记录:

[deployer@prod-mongo ~]$ sudo systemctl status mongod.service

mongod.service - SYSV: Mongo is a scalable, document-oriented database.
   Loaded: loaded (/etc/rc.d/init.d/mongod)
   Active: failed (Result: exit-code) since Tue 2015-05-12 04:42:10 UTC; 42s ago
  Process: 22881 ExecStart=/etc/rc.d/init.d/mongod start (code=exited, status=1/FAILURE)

May 11 04:42:10 ip-xx-xx-xx-xx.local runuser[22887]: pam_unix(runuser:session): session opened for user mongod by (uid=0)
May 11 04:42:10 ip-xx-xx-xx-xx.localdomain runuser[22887]: pam_unix(runuser:session): session closed for user mongod
May 11 04:42:10 ip-xx-xx-xx-xx.local mongod[22881]: Starting mongod: [FAILED]
May 11 04:42:10 ip-xx-xx-xx-xx.local systemd[1]: mongod.service: control process exited, code=exited status=1
May 11 04:42:10 ip-xx-xx-xx-xx.local systemd[1]: Failed to start SYSV: Mongo is a scalable, document-oriented database..
May 11 04:42:10 ip-xx-xx-xx-xx.local systemd[1]: Unit mongod.service entered failed state.

我关注了各种文章和博客文章以及 StackExchange 答案，但没有得到任何解决方案。我错过了什么吗？

更新:如果我直接从普通用户运行 mongodb 服务，如下所示:sudo mongod --logpath ~/mongod.log - -dbpath ~/mongodata，则该服务正常启动。

我们尝试将 pid 文件的路径更改为另一个目录，但也没有帮助。

最佳答案

我猜你正在运行一种使用 SELinux 的 Linux(可能是 RHEL 或 CentOS 7？)

如果是这样，问题是您的 /mongo/ 目录上没有允许访问守护程序的许可策略(例如 mongod 服务。)

来自维基百科:

SELinux can potentially control which activities a system allows each user, process and daemon, with very precise specifications. However, it is mostly used to confine daemons[citation needed] like database engines or web servers that have more clearly defined data access and activity rights. This limits potential harm from a confined daemon that becomes compromised. Ordinary user-processes often run in the unconfined domain, not restricted by SELinux but still restricted by the classic Linux access rights

要检查这是否是问题，请在 shell 中尝试:

sudo setenforce 0

这应该会禁用 SELinux 策略并允许服务运行。

如需更持久的解决方案，请参阅 https://wiki.centos.org/HowTos/SELinux

关于mongodb - 在 CentOS 7 上无法启动 MongoDB 3.0.2 服务，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/30182016/