This version of the documentation is archived and no longer supported.

Install MongoDB Enterprise on Red Hat Enterprise or CentOS


Use this tutorial to install MongoDB Enterprise on Red Hat Enterprise Linux or CentOS Linux versions 5, 6, and 7 from .rpm packages.

Platform Support

This installation guide only supports 64-bit systems. See Platform Support for details.


MongoDB provides officially supported Enterprise packages in their own repository. This repository contains the following packages:

Init Scripts

The mongodb-enterprise package includes various init scripts, including the init script /etc/rc.d/init.d/mongod.

The package configures MongoDB using the /etc/mongod.conf file in conjunction with the init scripts. See the Configuration File reference for documentation of settings available in the configuration file.

As of version 3.0.15, there are no init scripts for mongos. The mongos process is used only in sharding. You can use the mongod init script to derive your own mongos init script.


Use the provided distribution packages as described in this page if possible. These packages will automatically install all of MongoDB’s dependencies, and are the recommended installation method.

The default /etc/mongod.conf configuration file supplied by the 3.0 series packages has bind_ip set to by default. Modify this setting as needed for your environment before initializing a replica set.

Changed in version 2.6: The package structure and names have changed as of version 2.6. For instructions on installation of an older release, please refer to the documentation for the appropriate version.

Install MongoDB Enterprise

When you install the packages for MongoDB Enterprise, you choose whether to install the current release or a previous one. This procedure describes how to do both.


Configure repository.

Create an /etc/yum.repos.d/mongodb-enterprise.repo file so that you can install MongoDB enterprise directly, using yum.

For the latest 3.0 release of MongoDB Enterprise

Use the following repository file:

name=MongoDB Enterprise Repository

For a specific version of MongoDB Enterprise

To install MongoDB Enterprise packages from a specific release series, such as 2.4 or 2.6, you can specify the release series in the repository configuration. For example, to restrict your system to the 2.6 release series, create a /etc/yum.repos.d/mongodb-enterprise-2.6.repo file to hold the following configuration information for the MongoDB Enterprise 2.6 repository:

name=MongoDB Enterprise 2.6 Repository

.repo files for each release can also be found in the repository itself. Remember that odd-numbered minor release versions (e.g. 2.5) are development versions and are unsuitable for production deployment.


Install the MongoDB Enterprise packages and associated tools.

You can install either the latest 3.0 release of MongoDB Enterprise or a specific version of MongoDB Enterprise.

To install the latest 3.0 release of MongoDB Enterprise, issue the following command:

sudo yum install -y mongodb-enterprise

Optional: Manage Installed Version

Install a specific release of MongoDB Enterprise.

Specify each component package individually and append the version number to the package name, as in the following example that installs the 2.6.1 release of MongoDB:

sudo yum install -y mongodb-enterprise-2.6.1 mongodb-enterprise-server-2.6.1 mongodb-enterprise-shell-2.6.1 mongodb-enterprise-mongos-2.6.1 mongodb-enterprise-tools-2.6.1

Pin a specific version of MongoDB Enterprise.

Although you can specify any available version of MongoDB Enterprise, yum will upgrade the packages when a newer version becomes available. To prevent unintended upgrades, pin the package. To pin a package, add the following exclude directive to your /etc/yum.conf file:


Previous versions of MongoDB packages use different naming conventions. See the 2.4 version of documentation for more information.


When the install completes, you can run MongoDB.

Install MongoDB Enterprise From Tarball

While you should use the .rpm packages as previously described, you may also manually install MongoDB using the tarballs.

First you must install any dependencies as appropriate:

Version 5
yum install perl cyrus-sasl cyrus-sasl-plain cyrus-sasl-gssapi krb5-libs \
            lm_sensors net-snmp openssl popt rpm-libs tcp_wrappers zlib
Version 6
yum install cyrus-sasl cyrus-sasl-plain cyrus-sasl-gssapi krb5-libs \
            net-snmp openssl
Version 7
yum install cyrus-sasl cyrus-sasl-plain cyrus-sasl-gssapi krb5-libs \
            lm_sensors-libs net-snmp-agent-libs net-snmp openssl rpm-libs \

To perform the installation, see Install MongoDB Enterprise From Tarball.

Run MongoDB Enterprise


Configure SELinux


You must configure SELinux to allow MongoDB to start on Red Hat Linux-based systems (Red Hat Enterprise Linux or CentOS Linux).

To configure SELinux, administrators have three options:


All three options require root privileges. The first two options each requires a system reboot and may have larger implications for your deployment.

  • Disable SELinux entirely by changing the SELINUX setting to disabled in /etc/selinux/config.

  • Set SELinux to permissive mode in /etc/selinux/config by changing the SELINUX setting to permissive .



    You can use setenforce to change to permissive mode; this method does not require a reboot but is not persistent.

  • Enable access to the relevant ports (e.g. 27017) for SELinux if in enforcing mode. See Default MongoDB Port for more information on MongoDB’s default ports. For default settings, this can be accomplished by running

    semanage port -a -t mongod_port_t -p tcp 27017


    On RHEL 7.0, if you change the data path, the default SELinux policies will prevent mongod from having write access on the new data path if you do not change the security context.

You may alternatively choose not to install the SELinux packages when you are installing your Linux operating system, or choose to remove the relevant packages. This option is the most invasive and is not recommended.

Data Directories and Permissions


On RHEL 7.0, if you change the data path, the default SELinux policies will prevent mongod from having write access on the new data path if you do not change the security context.

The MongoDB instance stores its data files in /var/lib/mongo and its log files in /var/log/mongodb by default, and runs using the mongod user account. You can specify alternate log and data file directories in /etc/mongod.conf. See systemLog.path and storage.dbPath for additional information.

If you change the user that runs the MongoDB process, you must modify the access control rights to the /var/lib/mongo and /var/log/mongodb directories to give this user access to these directories.



Start MongoDB.

You can start the mongod process by issuing the following command:

sudo service mongod start

Verify that MongoDB has started successfully

You can verify that the mongod process has started successfully by checking the contents of the log file at /var/log/mongodb/mongod.log for a line reading

[initandlisten] waiting for connections on port <port>

where <port> is the port configured in /etc/mongod.conf, 27017 by default.

You can optionally ensure that MongoDB will start following a system reboot by issuing the following command:

sudo chkconfig mongod on

Stop MongoDB.

As needed, you can stop the mongod process by issuing the following command:

sudo service mongod stop

Restart MongoDB.

You can restart the mongod process by issuing the following command:

sudo service mongod restart

You can follow the state of the process for errors or important messages by watching the output in the /var/log/mongodb/mongod.log file.


Begin using MongoDB.

To help you start using MongoDB, MongoDB provides Getting Started Guides in various driver editions. See Getting Started for the available editions.

Before deploying MongoDB in a production environment, consider the Production Notes document.

Later, to stop MongoDB, press Control+C in the terminal where the mongod instance is running.

Uninstall MongoDB

To completely remove MongoDB from a system, you must remove the MongoDB applications themselves, the configuration files, and any directories containing data and logs. The following section guides you through the necessary steps.


This process will completely remove MongoDB, its configuration, and all databases. This process is not reversible, so ensure that all of your configuration and data is backed up before proceeding.


Stop MongoDB.

Stop the mongod process by issuing the following command:

sudo service mongod stop

Remove Packages.

Remove any MongoDB packages that you had previously installed.

sudo yum erase $(rpm -qa | grep mongodb-enterprise)

Remove Data Directories.

Remove MongoDB databases and log files.

sudo rm -r /var/log/mongodb
sudo rm -r /var/lib/mongo