Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Series of issues with Fedora 17 and MongoDB 2.2.1
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Erik Squires  
View profile  
 More options Nov 10 2012, 2:54 pm
From: Erik Squires <erik.squi...@gmail.com>
Date: Sat, 10 Nov 2012 11:54:57 -0800 (PST)
Local: Sat, Nov 10 2012 2:54 pm
Subject: Series of issues with Fedora 17 and MongoDB 2.2.1

I'm running fairly recent Fedora 17, 64 bit.  I've discovered several
installation problems following the
instructions from http://docs.mongodb.org/manual/tutorial/install-mongodb-on-redhat-cen...

To summarize:

SELinux:

   1. Get attr on /  fails.  
   2. Need to:  semanage port -a -t mongod_port_t -p tcp 28017

These I have of course been able to work around.  

In addition I have discovered the following other issues, not related to
SELinux:

   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.
   2. /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
   mongod:mongod /var/run/mongodb
   3. 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)
   4. 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.

I'm pretty surprised others aren't running into an issue as I'm doing this
with a fairly clean install of Fedora. The only things I have really
changed are updated, and installed Sun JDK.

Regards,

Erik


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Mark Hillick  
View profile  
 More options Nov 19 2012, 7:35 am
From: Mark Hillick <m...@10gen.com>
Date: Mon, 19 Nov 2012 04:35:43 -0800 (PST)
Local: Mon, Nov 19 2012 7:35 am
Subject: Re: Series of issues with Fedora 17 and MongoDB 2.2.1

Hi Erik,

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
   mongod:mongod /var/run/mongodb

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
stage?

I believe that our documentation on Fedora needs to be improved and I will
investigate this.

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.

Thanks

Mark


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »