運行yum命令查看MongoDB的包信息 [root@vm ~]# yum info mongo-10gen （提示沒有相關匹配的信息，） 說明你的centos系統(tǒng)中的yum源不包含MongoDB的相關資源，所以要在使用yum命令安裝MongoDB前需要增加yum源，也就是在 /etc/yum.repos.d/目錄中增加 *.repo yum源配置文件

<span style="font-family: Monaco, 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', Consolas, 'Courier New', monospace; line-height: 18px; background-color: rgb(250, 250, 250);">我們這里就將該文件命名為：/etc/yum.repos.d/10gen.repo</span>

（1）安裝32位yum適用的RPM包，編輯/etc/yum.repos.d/10gen.repo，加入以下代碼： [10gen] name=10gen Repository baseurl=http://downloads-distro.mongodb.org/repo/redhat/os/i686 gpgcheck=0

安裝服務器端： [root@vm ~]# yum install mongo-10gen-server 因為mongo-10gen-server包依賴于mongo-10gen，所以安裝了服務器后就不需要單獨安裝客戶端工具包mongo-10gen了 單獨安裝可客戶端： [root@vm ~]# yum install mongo-10gen

（2）安裝成功后，可以通過腳本來控制啟動/停止/重新啟動 /etc/init.d/mongodb start/stop/restart （3）這時候查看系統(tǒng)服務： chkconfig --list （4）會有一個叫 mongod 的服務了，將它設為開機啟動： chkconfig --level 345 mongod on （5）然后啟動它： service mongod start （6）這時候再查看該服務用的哪個端口： netstat -atln

（6）驗證MongoDB 可以通過檢查日志文件/var/log/mongodb/mongod.log的內容來判斷mongod進程是否正常運行。 也可以執(zhí)行命令： $ sudo chkconfig mongod on 要停止MongoDB，執(zhí)行： $ sudo service mongod stop 要重啟MongoDB，執(zhí)行： $ sudo service mongod restart

1：After upgrading MongoDB from version 2.4 to 2.6, I am not able to connect to it from another machine. The firewall has been checked to ensure that port 27017 is opened for the machine that I want to connect from. So what else could go wrong? Well, I was impatient and turned to you know what… Google search. According to this link: https://groups.google.com/forum/#!msg/mongodb-user/yhf05AW-hK8/YqES0cVIXlUJ, the problem is due to the database is bound to only local IP. Indeed, this was the case, and I could have found it out very easily had I run the netstat command: # netstat -tpln Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 127.0.0.1:27017 0.0.0.0:* LISTEN 10122/mongod To fix this, modify /etc/mongod.conf to include your server’s IP. Make sure you use ‘;’ instead of ‘,’ to list IP addresses. # Listen to local interface only. Comment out to listen on all interfaces. bind_ip=127.0.0.1;123.123.123.123

</pre><pre name="code" class="plain">http://blog.khmersite.net/2014/05/mongodb-warning-failed-to-connect/

I could not understand what bind_ip in mongodb is. I could make a remote connection from desktop to the EC2 machine by having bind_ip = 0.0.0.0, but could not make it work with bind_ip = 127.0.0.1. Please explain me what bind_ip is and why it works for 0.0.0.0 and not for 127.0.0.1. For reference from mongodb docs: bind_ip Default: All interfaces. Set this option to configure the mongod or mongos process to bind to and listen for connections from applications on this address. You may attach mongod or mongos instances to any interface; however, if you attach the process to a publicly accessible interface, implement proper authentication or firewall restrictions to protect the integrity of your database. You may concatenate a list of comma separated values to bind mongod to multiple IP addresses. You can't access your machine when you bind it to 127.0.0.1 on EC2. That's not a bug, it's reasoned by the network interface bindings. 127.0.0.1 will only bind to the loopback interface (so you will only be able to access it locally), while 0.0.0.0 will bind it to all network interfaces that are available. That's why you can access your mongodb on EC2 when you bind it to 0.0.0.0(as it's available through the internet now) and not via 127.0.0.1. For local servers (like a WAMP or a local mongodb server) that won't look different to you, but for that case you should also thing that binding to 0.0.0.0 for local servers might make them available over all network interfaces (so it might be public for someone who knows your IP, if there is no firewall!) Read on a similar question on Server Fault here.

http://stackoverflow.com/questions/17588876/mongodb-conf-bind-ip-127-0-0-1-does-not-work-but-0-0-0-0-works