-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Packaging
-
Labels:
-
Environment:[vagrant@vagrant-f19 ~]$ uname -a
Linux vagrant-f19 3.9.5-301.fc19.x86_64 #1 SMP Tue Jun 11 19:39:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
The vagrant box came from here:
[https://dl.dropboxusercontent.com/u/1251103/fedora-19-vagrant.box]
-
ALL
After installing the enterprise server package (sudo yum install mongodb-enterprise-unstable-server), starting the mongod service fails:
[vagrant@vagrant-f19 sync]$ sudo service mongod start Starting mongod (via systemctl): Job for mongod.service failed. See 'systemctl status mongod.service' and 'journalctl -xn' for details. [FAILED] [vagrant@vagrant-f19 sync]$ 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 Thu 2013-10-17 11:02:04 EDT; 8s ago Process: 1775 ExecStart=/etc/rc.d/init.d/mongod start (code=exited, status=1/FAILURE)
The equivalent community package, mongodb-org-unstable-server, does not have this problem---the mongod service starts just fine.
I ran "diff" on the /etc/init.d/mongod init scripts for mongodb-org-unstable-server and mongodb-enterprise-unstable-server, which showed that the two init scripts are identical. The /etc/rc.d/init.d/mongod files are also identical between the two packages.
- duplicates
-
-
- Closed
-