Install MongoDB Enterprise on Red Hat Enterprise or CentOS¶
On this page
Use this tutorial to install MongoDB Enterprise on Red Hat Enterprise Linux or CentOS
Linux versions 5, 6, and 7 from
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:
This package is a
metapackagethat will automatically install the four component packages listed below.
This package contains the
mongoddaemon and associated configuration and init scripts.
This package contains the
This package contains the
mongodb-enterprise package includes various init scripts, including the init script
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.
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.
/etc/mongod.conf configuration file supplied by the
3.0 series packages has
bind_ip set to
127.0.0.1 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.
/etc/yum.repos.d/mongodb-enterprise.repo file so that
you can install MongoDB enterprise directly, using
For the latest 3.0 release of MongoDB Enterprise¶
Use the following repository file:
[mongodb-enterprise] name=MongoDB Enterprise Repository baseurl=https://repo.mongodb.com/yum/redhat/$releasever/mongodb-enterprise/3.0/$basearch/ gpgcheck=0 enabled=1
For a specific version of MongoDB Enterprise¶
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,
to hold the following configuration information for the MongoDB
Enterprise 2.6 repository:
[mongodb-enterprise-2.6] name=MongoDB Enterprise 2.6 Repository baseurl=https://repo.mongodb.com/yum/redhat/$releasever/mongodb-enterprise/2.6/$basearch/ gpgcheck=0 enabled=1
.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
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
directive to your
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 \ tcp_wrappers-libs
To perform the installation, see Install MongoDB Enterprise From Tarball.
Run MongoDB Enterprise¶
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
Disable SELinux entirely by changing the
Set SELinux to
/etc/selinux/configby changing the
You can use
setenforceto 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
enforcingmode. 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
mongodfrom 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
and its log files in
/var/log/mongodb by default,
and runs using the
user account. You can specify alternate log and data file
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/log/mongodb directories to give this user access to these
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
for a line reading
[initandlisten] waiting for connections on port <port>
<port> is the port configured in
27017 by default.
You can optionally ensure that MongoDB will start following a system reboot by issuing the following command:
sudo chkconfig mongod on
Begin using MongoDB.¶
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.
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.
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