I believe that most of the issues that you're referring to are all due to
SELinux. Disabling SELinux results in a MongoDB being installed ok,
however, this is not the solution that you'd like I presume (i.e. get it to
work with SELinux enabled would be desirable).
1. Mongo doesn't seem to take the configuration option for the db path,
so you must create /data/db. That is, /etc/mongod.conf is correct and sets
the dbpath to a path that exists, but it won't accept it.
I'm not fully sure what you are saying is the issue here is? The default
path is /var/lib/mongo. Do you want to run mongod with "--dbpath"? This
isn't the correct way to do it with the conf file.
1. /var/run/mongodb is not created on install. You must create
/var/run/mongodb so that the PID may be stored. also must do chown
I've created a server ticket requesting this feature here, please vote and
contribute to the ticket. The "chown" is natural given that MongoDB is
install under the "mongod" user. I believe the lack of a PID file under
/var/run is consistent across all platforms for MongoDB installations.
1. Installing mongo-10gen-server will install and set it to start on
reboot. Turn it off until you resolve the next issue (chkconfig mongod off)
2. mongod starts, but doesn't know it. Attempt to start via service
mongod start pauses for several minutes. The Mongod is running, you can
connect to it, query, etc. but service doesn't know it, so it will hang. If
you put it to auto-start it will hang your boot process.
Can you confirm your SELinux settings (/etc/sysconfig/selinux) at the above
I believe that our documentation on Fedora needs to be improved and I will
There is another ticket <https://jira.mongodb.org/browse/SERVER-7285>currently
under investigation regarding issues starting MongoDB on Fedora. If you
have anything to add there, please do and vote on the feature.