本文共 6250 字，大约阅读时间需要 20 分钟。
[10gen]name=10gen Repositorybaseurl=http://downloads-distro.mongodb.org/repo/redhat/os/i686gpgcheck=0 enabled=1
Issue the following command (as root or with sudo) to install the latest stable version of MongoDB and the associated tools:
yum install mongo-10gen mongo-10gen-server
When this command completes, you have successfully installed MongoDB!
when it prompts error info, you can change the "gpgcheck=1" to "gpgcheck=0" in /etc/yum.conf
Package mongo-10gen-2.4.4-mongodb_1.i686.rpm is not signed
if the previous solution does not solve the issue above, please use the rpm command as below.
rpm -ivh mongo-10gen-2.4.4-mongodb_1.i686.rpm
rpm -ivh mongo-10gen-server-2.4.4-mongodb_1.i686.rpm
These packages configure MongoDB using the /etc/mongod.conf file in conjunction with the . You can find the init script at/etc/rc.d/init.d/mongod.
This MongoDB instance will store its data files in the /var/lib/mongoand its log files in /var/log/mongo, and run using the mongod user account.
Start the process by issuing the following command (as root, or with sudo):
service mongod start
You can verify that the process has started successfully by checking the contents of the log file at /var/log/mongo/mongod.log.
Fri Jun 7 08:12:56.944 [initandlisten] MongoDB starting : pid=5098 port=27017 d bpath=/var/lib/mongo 32-bit host=lx.sirius.com
Fri Jun 7 08:12:56.945 [initandlisten] Fri Jun 7 08:12:56.945 [initandlisten] ** NOTE: This is a 32 bit MongoDB binary . Fri Jun 7 08:12:56.945 [initandlisten] ** 32 bit builds are limited to le ss than 2GB of data (or less with --journal). Fri Jun 7 08:12:56.945 [initandlisten] ** Note that journaling defaults t o off for 32 bit and is currently off. Fri Jun 7 08:12:56.945 [initandlisten] ** See http://dochub.mongodb.org/c ore/32bit Fri Jun 7 08:12:56.945 [initandlisten] Fri Jun 7 08:12:56.945 [initandlisten] db version v2.4.4 Fri Jun 7 08:12:56.945 [initandlisten] git version: 4ec1fb96702c9d4c57b1e06dd34 eb73a16e407d2 Fri Jun 7 08:12:56.945 [initandlisten] build info: Linux bs-linux32.10gen.cc 2. 6.21.7-2.fc8xen #1 SMP Fri Feb 15 12:39:36 EST 2008 i686 BOOST_LIB_VERSION=1_49 Fri Jun 7 08:12:56.945 [initandlisten] allocator: system Fri Jun 7 08:12:56.945 [initandlisten] options: { config: "/etc/mongod.conf", d bpath: "/var/lib/mongo", fork: "true", logappend: "true", logpath: "/var/log/mon go/mongod.log", pidfilepath: "/var/run/mongodb/mongod.pid" } Fri Jun 7 08:12:56.976 [FileAllocator] allocating new datafile /var/lib/mongo/l ocal.ns, filling with zeroes... Fri Jun 7 08:12:56.976 [FileAllocator] creating directory /var/lib/mongo/_tmp Fri Jun 7 08:12:57.132 [FileAllocator] done allocating datafile /var/lib/mongo/ local.ns, size: 16MB, took 0.149 secs Fri Jun 7 08:12:57.132 [FileAllocator] allocating new datafile /var/lib/mongo/l ocal.0, filling with zeroes... Fri Jun 7 08:12:57.254 [FileAllocator] done allocating datafile /var/lib/mongo/ local.0, size: 16MB, took 0.121 secs Fri Jun 7 08:12:57.258 [initandlisten] command local.$cmd command: { create: "s tartup_log", size: 10485760, capped: true } ntoreturn:1 keyUpdates:0 reslen:37 283ms Fri Jun 7 08:12:57.261 [websvr] admin web console waiting for connections on po rt 28017 Fri Jun 7 08:12:57.288 [initandlisten] waiting for connections on port 27017
You may optionally, ensure that MongoDB will start following a system reboot, by issuing the following command (with root privileges:)
chkconfig mongod on How to monitor the mongod process.
[root@lx updates]# netstat -lanp | grep "27017"
tcp 0 0 0.0.0.0:27017 0.0.0.0:* LISTEN 5098/mongod unix 2 [ ACC ] STREAM LISTENING 21364 5098/mongod /tmp/mongodb-27017.sock [root@lx updates]#Stop the process by issuing the following command (as root, or with sudo):
service mongod stop
You can restart the process by issuing the following command (as root, or with sudo):
service mongod restart
Follow the state of this process by watching the output in the/var/log/mongo/mongod.log file to watch for errors or important messages from the server.
As of the current release, there are no for . is only used in sharding deployments and typically do not run on the same systems where runs. You can use the mongodbscript referenced above to derive your own control script.
You must SELinux to allow MongoDB to start on Fedora systems. Administrators have two options:
Among the tools included in the mongo-10gen package, is the shell. You can connect to your MongoDB instance by issuing the following command at the system prompt:
mongo
This will connect to the database running on the localhost interface by default. At the prompt, issue the following two commands to insert a record in the “test” of the (default) “test” database and then retrieve that document.
> db.test.save( { a: 1 } )> db.test.find() [root@lx updates]# mongo
MongoDB shell version: 2.4.4 connecting to: test Welcome to the MongoDB shell. For interactive help, type "help". For more comprehensive documentation, see http://docs.mongodb.org/ Questions? Try the support group http://groups.google.com/group/mongodb-user Server has startup warnings: Fri Jun 7 08:12:56.945 [initandlisten] Fri Jun 7 08:12:56.945 [initandlisten] ** NOTE: This is a 32 bit MongoDB binary. Fri Jun 7 08:12:56.945 [initandlisten] ** 32 bit builds are limited to less than 2GB of data (or less with --journal). Fri Jun 7 08:12:56.945 [initandlisten] ** Note that journaling defaults to off for 32 bit and is currently off. Fri Jun 7 08:12:56.945 [initandlisten] ** See http://dochub.mongodb.org/core/32bit Fri Jun 7 08:12:56.945 [initandlisten]
Reference
转载地址：http://lpztd.baihongyu.com/