I'm not sure where this issue is coming from, but my experiences while not ideal are quite different on Fedora 17
I have alsways installed all my copies of Mongo on F16 and F17 from the mongodb Repo using "yum install mongo-10gen mongo-10gen-server"
There IS a failure mode, but for me its not related to permissions, systemd when presented with a new init.d script, reads the script and creates the systemd unit file automaticaly. The mongod init.d script has an incorrect pidfile path which points to a non-existant pidfile.
changing this comment to (for the default install)
- pidfile: /var/lib/mongo/mongod.lock
sudo systemctl --system daemon-reload
causes systemd to reimport the init.d script and rebuild the systemd unit file.
So now systemd can find the mongod.lock file which contains the running server pid.
Without this two things will happen.
1. Starting mongod with
service mongod start
will stall, as its waiting for the pid file to be created, mongod actualy starts up, but the command never returns.
2. If you have executed
sudo chkconfig mongod on
to get mongo to startup at boot, then your system will hard hang on restart, and you will have to use the emergency console to recover your system.