I’m not Tilo and if you check Tilo’s comment time, I think that he’s not answering your question very soon.

But yes, I’m not huge fan of custom hacks to init scripts, but I think that you just have “wrong” single quotes on you config, it should be:

MONGO_DBPATH=`grep '^dbpath' /etc/mongod.conf | cut -d'=' -f2`

Good Afternoon, when I used your instruction then after I restart mongod or check status I got this message. See below
[root@ip-10-174-15-18 ~]# service mongod status
cut: the delimiter must be a single character
Try `cut –help’ for more information.
[root@ip-10-174-15-18 ~]# /etc/init.d/mongod start
cut: the delimiter must be a single character
Try `cut –help’ for more information.
Starting mongod: [ OK ]
forked process: 22975

please help thanks a lot..

Thanks!

like this :

# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
...
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 27017 -j ACCEPT
COMMIT


Could you post your /etc/sysconfig/iptables file content?

This configuration is not working in my fedora 15. Someone clue what the problem is?

MongoDB shell version: 1.8.1
connecting to: 87.106.244.253:27017/test
Thu May 19 15:36:29 Error: couldn’t connect to server 87.106.244.253:27017 shell/mongo.js:81
exception: connect failed

add these two lines towards the top of the /etc/init.d/mongod file:

MONGO_DBPATH=`grep ‘^dbpath’ /etc/mongod.conf | cut -d’=’ -f2` # get dbpath from config
MONGO_LOCKFILE=”$MONGO_DBPATH/mongod.lock”

replace the line containing “killproc” with:

killproc -p $MONGO_LOCKFILE -t30 -TERM /usr/bin/mongod

I’m not sure is it possible to use “Shell Fork Bomb Protection” simultaneously with MongoDB, but maybe you could use /etc/security/limits.conf file to limit certain users or groups processes, like following:

<domain>        <type>  <item>  <value>
someuser        hard    nproc     20
@somegroup      hard    nproc     15

I was wondering if there is a way to enable fork bomb protection and keep mongo happy?

Only one thing – on the last step (4.2) I get this:

Flushing firewall rules: [ OK ]
Setting chains to policy ACCEPT: mangle filter nat [ OK ]
Unloading iptables modules: [ OK ]
Applying iptables firewall rules: iptables-restore: line 1 failed [FAILED]

Is this a problem? I added the line exactly as shown “-A RH-Firewall-1-INPUT -m state –state NEW -m tcp -p tcp –dport 27017 -j ACCEPT”

Thanks

Everybody with following problem:

/etc/init.d/mongod: line 25: /etc/sysconfig/mongod: No such file or directory
Starting mongod: runuser: user mongod does not exist

Old repositories caused this problem (they worked nice with 1.2.x versions, but not with 1.4.x versions and now this guide installs 1.6.x version), I updated this guide to use MongoDB own repositories and now I tested this new installation method on different systems and it worked smoothly.

So if you have old packages installed then simply remove them, with following command:

yum remove mongo mongo-server

And then follow this guide.

get this error on service mongod start

PLEASE HELP?

same

[root@main ~]# service mongod start
/etc/init.d/mongod: line 24: /etc/sysconfig/mongod: No such file or directory
Starting mongod: warning: some regex utf8 things will not work. pcre build doesn’t have –enable-unicode-properties
forked process: 13626
all output going to: /var/log/mongo/mongod.log
[root@main ~]# [ OK ]

Though it seems to start okay.

The /etc/sysconfig/mongod file should not be created.

You possibly mean or try to find /etc/sysconfig/iptables, /etc/mongod.conf or /etc/init.d/mongod file?