Use this tutorial to install MongoDB 8.0 Community Edition on Red Hat Enterprise Linux, CentOS Linux, or Oracle Linux [1] using the yum package manager.
This tutorial installs MongoDB 8.0 Community Edition. To install a different version of MongoDB Community, use the version drop-down menu in the upper-left corner of this page to select the documentation for that version.
MongoDB 8.0 Community Edition supports the following 64-bit versions of Red Hat Enterprise Linux (RHEL), CentOS Linux, Oracle Linux [1], Rocky Linux, and AlmaLinux [2] on x86_64 architecture:
RHEL / CentOS Stream / Oracle / Rocky / AlmaLinux 9
RHEL / CentOS Stream / Oracle / Rocky / AlmaLinux 8
MongoDB only supports the 64-bit versions of these platforms.
MongoDB 8.0 Community Edition on RHEL / CentOS / Oracle / Rocky / AlmaLinux also supports the ARM64 architecture on select platforms.
See Platform Support for more information.
Before deploying MongoDB in a production environment, consider the Production Notes for Self-Managed Deployments document which offers performance considerations and configuration recommendations for production MongoDB deployments.
Follow these steps to install MongoDB Community Edition using the yum package manager.
Create a /etc/yum.repos.d/mongodb-org-8.0.repo file so that you can install MongoDB directly using yum:
[mongodb-org-8.0]name=MongoDB Repositorybaseurl=https://repo.mongodb.org/yum/redhat/9/mongodb-org/8.0/x86_64/gpgcheck=1enabled=1gpgkey=https://pgp.mongodb.com/server-8.0.asc[mongodb-org-8.0]name=MongoDB Repositorybaseurl=https://repo.mongodb.org/yum/redhat/8/mongodb-org/8.0/x86_64/gpgcheck=1enabled=1gpgkey=https://pgp.mongodb.com/server-8.0.ascYou can also download the .rpm files directly from the MongoDB repository . Downloads are organized by Red Hat / CentOS version (e.g. 9), then MongoDB release version (e.g. 8.0), then architecture (e.g. x86_64).
Prior to MongoDB 5.0, odd-numbered MongoDB release versions, such as 4.3, were development releases. Beginning with MongoDB 5.1, MongoDB has quarterly rapid releases. For more information on the differences between rapid and long-term support releases, see MongoDB Versioning.
To install the latest stable version of MongoDB, issue the following command:
sudo yum install -y mongodb-orgTo install a specific release of MongoDB, specify each component package individually and append the version number to the package name.
sudo yum install -y \ mongodb-org-8.0.12 \ mongodb-org-database-8.0.12 \ mongodb-org-server-8.0.12 \ mongodb-mongosh \ mongodb-org-mongos-8.0.12 \ mongodb-org-tools-8.0.12 \ mongodb-org-database-tools-extra-8.0.12yum automatically upgrades packages when newer versions become available. If you want to prevent MongoDB upgrades, pin the package by adding the following exclude directive to your /etc/yum.conf file:
exclude=mongodb-org,mongodb-org-database,mongodb-org-server,mongodb-mongosh,mongodb-org-mongos,mongodb-org-toolsMost Unix-like operating systems limit the system resources that a process may use. These limits may negatively impact MongoDB operation, and should be adjusted. See UNIX ulimit Settings for Self-Managed Deployments for the recommended settings for your platform.
If the ulimit value for number of open files is under 64000, MongoDB generates a startup warning.
By default, MongoDB runs using the mongod user account and uses the following default directories:
/var/lib/mongo (the data directory)
/var/log/mongodb (the log directory)
The package manager creates the default directories during installation. The owner and group name are mongod.
To use a data directory and/or log directory other than the default directories:
Create the new directory or directories.
Edit the configuration file /etc/mongod.conf and modify the following fields accordingly:
storage.dbPath to specify a new data directory path (e.g. /some/data/directory)
systemLog.path to specify a new log file path (e.g. /some/log/directory/mongod.log)
Ensure that the user running MongoDB has access to the directory or directories:
sudo chown -R mongod:mongod <directory>If you change the user that runs the MongoDB process, you must give the new user access to these directories.
Configure SELinux if enforced. See Configure SELinux.
Starting in MongoDB 5.0, a new SELinux policy is available for MongoDB installations that:
Use an .rpm installer.
Use default configuration settings.
Run on RHEL7 or later.
If your installation does not meet these requirements, refer to the SELinux Instructions for .tgz packages.
Ensure you have the following packages installed:
git
make
checkpolicy
policycoreutils
selinux-policy-devel
sudo yum install git make checkpolicy policycoreutils selinux-policy-develDownload the policy repository.
git clone https://github.com/mongodb/mongodb-selinuxBuild the policy.
Apply the policy.
Starting in MongoDB 5.1, you must run the following command from the directory into which the SELinux policy was previously cloned before you can downgrade to an earlier MongoDB version:
The SELinux policy is designed to work with the configuration that results from a standard MongoDB .rpm package installation. See standard installation assumptions for more details.
The SELinux policy is designed for mongod servers. It does not apply to other MongoDB daemons or tools such as:
The reference policy supplied by the SELinux Project includes a mongodb_admin macro. This macro is not included in the MongoDB SELinux policy. An administrator in the unconfined_t domain can manage mongod.
To uninstall the policy, go to the directory where you downloaded the policy repository and run:
Follow these steps to run MongoDB Community Edition on your system. These instructions assume that you are using the default settings.
Init System
To run and manage your mongod process, you will be using your operating system's built-in init system. Recent versions of Linux tend to use systemd (which uses the systemctl command), while older versions of Linux tend to use System V init (which uses the service command).
If you are unsure which init system your platform uses, run the following command:
ps --no-headers -o comm 1Then select the appropriate tab below based on the result:
systemd - select the systemd (systemctl) tab below.
init - select the System V Init (service) tab below.
You can start the mongod process by issuing the following command:
sudo systemctl start mongodIf you receive an error similar to the following when starting mongod:
Failed to start mongod.service: Unit mongod.service not found.
Run the following command first:
sudo systemctl daemon-reloadThen run the start command above again.
You can verify that the mongod process has started successfully by issuing the following command:
sudo systemctl status mongodYou can optionally ensure that MongoDB will start following a system reboot by issuing the following command:
sudo systemctl enable mongodAs needed, you can stop the mongod process by issuing the following command:
sudo systemctl stop mongodYou can restart the mongod process by issuing the following command:
sudo systemctl restart mongodYou can follow the state of the process for errors or important messages by watching the output in the /var/log/mongodb/mongod.log file.
You can start the mongod process by issuing the following command:
sudo service mongod startYou 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:
As needed, you can stop the mongod process by issuing the following command:
You can restart the mongod process by issuing the following command:
sudo service mongod restartYou can follow the state of the process for errors or important messages by watching the output in the /var/log/mongodb/mongod.log file.
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.
WarningThis 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 the mongod process by issuing the following command:
Remove any MongoDB packages that you had previously installed.
sudo yum erase $(rpm -qa | grep mongodb-org)Remove MongoDB databases and log files.
sudo rm -r /var/log/mongodbsudo rm -r /var/lib/mongoBy default, MongoDB launches with bindIp set to 127.0.0.1, which binds to the localhost network interface. This means that the mongod can only accept connections from clients that are running on the same machine. Remote clients will not be able to connect to the mongod, and the mongod will not be able to initialize a replica set unless this value is set to a valid network interface.
This value can be configured either:
For more information on configuring bindIp, see IP Binding in Self-Managed Deployments.
MongoDB Community Edition is available from its own dedicated repository, and contains the following officially-supported packages:
Package Name
Description
mongodb-org
A metapackage that automatically installs the component packages listed below.
mongodb-org-database
A metapackage that automatically installs the component packages listed below.
Package Name
Description
mongodb-org-server
Contains the mongod daemon, associated init script, and a configuration file (/etc/mongod.conf). You can use the initialization script to start mongod with the configuration file. For details, see the "Run MongoDB Community Edition" section, above.
mongodb-org-mongos
Contains the mongos daemon.
mongodb-mongosh
Contains the MongoDB Shell (mongosh).
mongodb-org-tools
A metapackage that automatically installs the component packages listed below:
Package Name
Description
mongodb-database-tools
Contains the following MongoDB database tools:
mongodb-org-database-tools-extra
Contains the install_compass script
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4