Sha*_*wal 7 amazon-ec2 mongodb amazon-web-services centos7
我们正在为Amazon EC2实例上的生产环境设置MongoDB服务器,但无法启动该服务.我已按照此文档进行设置.以下是我为设置服务器所采取的步骤:
添加以下内容 /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
Run Code Online (Sandbox Code Playgroud)
并使用安装MongoDB 3.0.2 sudo yum install -y mongodb-org-3.0.2
为数据,日志和日志创建了三个分区:
sudo mkdir /mongo
sudo mkdir /mongo/data
sudo mkdir /mongo/log
sudo mkdir /mongo/journal
Run Code Online (Sandbox Code Playgroud)
为三个单独的分区创建文件系统:
sudo mkfs.ext4 /dev/xvdb
sudo mkfs.ext4 /dev/xvdc
sudo mkfs.ext4 /dev/xvdd
Run Code Online (Sandbox Code Playgroud)
创建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
Run Code Online (Sandbox Code Playgroud)
并安装分区:
sudo mount /mongo/data
sudo mount /mongo/journal
sudo mount /mongo/log
Run Code Online (Sandbox Code Playgroud)
给定权限并创建链接
sudo chown mongod:mongod /mongo/data /mongo/journal /mongo/log
sudo ln -s /mongo/journal /mongo/data/journal
Run Code Online (Sandbox Code Playgroud)
配置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
Run Code Online (Sandbox Code Playgroud)
权限:
[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
Run Code Online (Sandbox Code Playgroud)
内 /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
Run Code Online (Sandbox Code Playgroud)
更改内部配置后 /etc/mongodb.conf
logpath=/mongo/log/mongod.log
dbpath=/mongo/data
Run Code Online (Sandbox Code Playgroud)
当我这样做时sudo service mongod start,我收到了这个错误:
Starting mongod (via systemctl): Job for mongod.service failed. See 'systemctl status mongod.service' and 'journalctl -xn' for details.
[FAILED]
Run Code Online (Sandbox Code Playgroud)
进一步记录:
[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.
Run Code Online (Sandbox Code Playgroud)
我已经关注了各种文章和博客文章以及StackExchange的答案,但没有得到任何解决方案.我错过了什么吗?
更新:如果我mongodb从普通用户直接运行这样的服务:sudo mongod --logpath ~/mongod.log --dbpath ~/mongodata那么这项服务正在正常启动.
我们尝试将pid文件的路径更改为另一个目录,这也没有帮助.
我猜您正在运行使用SELinux的Linux版本(也许是RHEL或CentOS 7?)
如果是这样,则问题是您的/mongo/目录上没有允许访问守护程序(如mongod服务)的宽松策略。
从维基百科:
SELinux可以用非常精确的规范来控制系统允许每个用户,进程和守护程序进行哪些活动。但是,它通常用于限制守护程序(需要引用),例如数据库引擎或Web服务器,这些守护程序具有更清晰的数据访问和活动权限。这限制了受限制的守护程序的潜在危害。普通用户进程通常在不受限制的域中运行,不受SELinux的限制,但仍受经典Linux访问权限的限制
要检查是否是问题所在,请在shell上尝试:
sudo setenforce 0
这应该禁用SELinux策略并允许服务运行。
有关更永久的解决方案,请参见https://wiki.centos.org/HowTos/SELinux
| 归档时间: |
|
| 查看次数: |
23372 次 |
| 最近记录: |