Use MongoDB to Store Application Data on Fedora 13
Traducciones al EspañolEstamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
This guide has been deprecated and is no longer being maintained.
MongoDB is a database engine that provides access to non-relational key-value databases. It is part of the growing NoSQL movement, which seeks to provide an alternative to traditional relational database management systems (RDBMS). In addition to its schema-free design and scalable architecture, MongoDB provides a JSON-based output format and specialized language specific bindings that make it particularly attractive for use in custom application development. Although MongoDB is a relatively new project and has not yet been packaged by most major operating system distributions, the software has been used in a number of large scale production deployments such as “GitHub”, “SourceForge”, and “DISQUS”.
Before installing MongoDB, it is assume that you have followed our Setting Up and Securing a Compute Instance. If you are new to Linux server administration, you may be interested in our introduction to Linux concepts guide, beginner’s guide and administration basics guide.
Issue the following command to ensure that your system and all installed software is up to date:
Download the latest binaries from the upstream source.; at the time of writing this is version 1.6.5. When downloading MongoDB, ensure that you download a version that is compiled for the proper system architecture. This document uses the 32-bit version; however, these steps will work for the 64-bit edition with a few modifications. Please note that the 32-bit version of MongoDB has a database size limit of 2 gigabytes. If you expect to store more than 2 gigabytes of data, ensure that you have deployed a 64-bit system and are using the 64-bit version of MongoDB.
cd /opt/ wget http://fastdl.mongodb.org/linux/mongodb-linux-i686-1.6.5.tgz tar zxvf mongodb-linux-i686-1.6.5.tgz mv mongodb-linux-i686-1.6.5 /opt/mongodb
MongoDB is now deployed in the
/opt/mongodb/ folder with the binaries located in the
/opt/mongodb/bin/ folder. In this example, it is assumed that all database files will be stored in the
/srv/db/mongodb folder and that log files will be stored in the
/srv/db/mongodb.log file. Issue the following commands to create this file and directory:
mkdir -p /srv/db/mongodb touch /srv/db/mongodb.log
In this example the name of the database will be
mongodb; however, you can modify this name with another name or naming scheme as needed.
When running software compiled or installed directly from sources provided by upstream developers, you are responsible for monitoring updates, bug fixes, and security issues. After becoming aware of releases and potential issues, update your software to resolve flaws and prevent possible system compromise. Monitoring releases and maintaining up to date versions of all software is crucial for the security and integrity of a system.
Please monitor the following MongoDB mailing lists for updates to ensure that you are aware of all updates to the software and can upgrade appropriately or apply patches and recompile as needed:
When upstream sources offer new releases, repeat the instructions for installing MongoDB and recompile your software when needed.
In typical installations, the MongoDB server process is controlled using command line arguments to binaries located at
/opt/mongodb/bin/mongod. In order to simplify commands, you can create control scripts named
mongodb-stop in the
/opt/bin/ directory. Issue the following commands to create the required directories:
mkdir /opt/bin/ mkdir /opt/config/
Issue the following sequence of commands to download the scripts and set the permissions on these files:
cd /opt/bin/ wget -O mongodb-start http://www.linode.com/docs/assets/572-mongodb-start.sh wget -O mongodb-stop http://www.linode.com/docs/assets/573-mongodb-stop.sh chmod +x *
Review the contents of the
mongodb-stop and modify these files if your deployment requires an alternate initialization procedure. From now on, issuing
/opt/bin/mongodb-stop will start or stop the MongoDB process, respectively. The behavior of the
mongod process is controlled by the values set in
/opt/config/mongodb and use the following example as a template:
- File: /opt/config/mongodb
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
# Configuration Options for MongoDB # # For More Information, Consider: # - Configuration Parameters: http://www.mongodb.org/display/DOCS/Command+Line+Parameters # - File Based Configuration: http://www.mongodb.org/display/DOCS/File+Based+Configuration dbpath = /srv/db/mongodb logpath = /srv/db/mongodb.log logappend = true bind_ip = 127.0.0.1 port = 27017 fork = true auth = true # noauth = true
This specifies a number of important options that you may modify to control the functionality of
dbpath option indicates that database files will be stored in
logpath directive indicates that MongoDB’s logs will be located in the
/srv/db/log/mongodb.log file, and that new log entries will be appended to the end of the log rather than overwriting existing log entries even after MongoDB restarts.
bind_ip option is not specified, MongoDB will bind to and listen for requests on all local IP addresses. In this case, MongoDB is configured to only listen for requests on the localhost interface. Modify this option to allow your MongoDB server to listen for requests on other IP addresses; however, consider the possible security implications of providing public access. The
port option in this file specifies the default port, but can be modified depending on your needs.
fork option to equal
true configures MongoDB to run as a daemon process in the background independently of the current user’s session. Please note that MongoDB will run under the user that executes the
mongodb-start script. We strongly recommend that this user not be root or another privileged user account. To provide additional security, it is recommended that you set the
auth option to
true in order to take advantage of MongoDB’s internal authentication capabilities. If you need to test the database without authentication, you can replace the
auth option to
We’ve also created a very basic “init script” as a wrapper around the
mongo-stop scripts described above. You will still need to modify and manage the configuration of your MongoDB server in the files above. This script only provides a means for ensuring that MongoDB will start at boot. Issue the following commands:
wget -O init-rpm.sh http://www.linode.com/docs/assets/571-mongodb-init-rpm.sh mv init-rpm.sh /etc/rc.d/init.d/mongodb chmod +x /etc/rc.d/init.d/mongodb /etc/init.d/mongodb chkconfig --add mongodb chkconfig mongodb on
You will also need to create a user and group for mongodb; issue the following command:
useradd -M -r --home-dir /opt/mongodb mongodb
Now issue the following command to ensure that the MongoDB user you just created will have access to all required files in the
chown mongodb:mongodb -R /srv/db/
To start and stop MongoDB using the init script, issue the appropriate command from the following:
/etc/init.d/mongodb start /etc/init.d/mongodb stop
Congratulations, you now have a fully functional installation of the MongoDB system.
Now that MongoDB is running properly, you can begin to explore some of its features. Most interaction with MongoDB is done via the rich set of language-specific drivers. There are also a number of tools in the
/opt/mongodb/bin/ directory that you might find useful for interacting with MongoDB databases. The
mongorestore for creating and restoring backups and snapshots as well
mongoimportjson for exporting individual collections in JSON format.
You can now fully enjoy application development with MongoDB!
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This page was originally published on