- Install MongoDB >
- Install MongoDB Community Edition >
- Install MongoDB Community Edition on Linux >
- Install MongoDB Community Edition on Red Hat or CentOS >
- Install MongoDB Community on Red Hat or CentOS Using .tgz Tarball
Install MongoDB Community on Red Hat or CentOS Using .tgz Tarball¶
Overview¶
Although the recommended procedure to install is through the
package manager, you can also
install by directly downloading the .tgz
file. The following
tutorial downloads the .tgz
tarball directly to install MongoDB
4.2 Community Edition on Red Hat Enterprise Linux, CentOS Linux,
or Oracle Linux [1] versions 6, 7, and 8.
This installation guide only supports 64-bit systems. See Supported Platforms for more information.
Windows Subsystem for Linux (WSL) - Unsupported
MongoDB does not support WSL, and users on WSL have encountered various issues installing on WSL. For examples, see:
Production Notes
Before deploying MongoDB in a production environment, consider the Production Notes document.
[1] | MongoDB only supports Oracle Linux running the Red Hat Compatible Kernel (RHCK). MongoDB does not support the Unbreakable Enterprise Kernel (UEK). |
Install MongoDB Community Edition¶
Note
To install a different version of MongoDB, please refer to that version’s documentation. To install the previous version, see the tutorial for version 4.0.
This installation guide only supports 64-bit systems. See Supported Platforms for more information.
Prerequisites¶
MongoDB .tar.gz
tarballs require installing the following
dependencies:
Procedure¶
Download the MongoDB .tgz
tarball.¶
Download the tarball for your system from the MongoDB Download Center.
Extract the files from the downloaded archive.¶
For example, from a system shell, you can extract using the tar
command:
Ensure the binaries are in a directory listed in your PATH
environment variable.¶
The MongoDB binaries are in the bin/
directory of the tarball.
You can either:
Copy the binaries into a directory listed in your
PATH
variable, such as/usr/local/bin
(Update/path/to/the/mongodb-directory/
with your installation directory as appropriate)Create symbolic links to the binaries from a directory listed in your
PATH
variable, such as/usr/local/bin
(Update/path/to/the/mongodb-directory/
with your installation directory as appropriate):
Run MongoDB Community Edition¶
Prerequisites¶
ulimit¶
Directory Paths¶
To Use Default Directories¶
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)
- ➤ If you installed via the package manager,
- The default directories are created, and the owner and group for
these directories are set to
mongod
. - ➤ If you installed by downloading the tarballs,
The default MongoDB directories are not created. To create the MongoDB data and log directories:
Tip
Depending on your user permission, you may need to use
sudo
to perform these operations.By default, MongoDB runs using the
mongod
user account. Once created, set the owner and group of these directories tomongod
:
To Use Non-Default Directories¶
To use a data directory and/or log directory other than the default directories:
Tip
Depending on your user permission, you may need to use sudo
to perform these operations.
Create the new directory or directories.
Edit the 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:
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.
Configure SELinux¶
Important
If SELinux is in enforcing
mode, you must customize your SELinux
policy for MongoDB.
The current SELinux Policy does not allow the MongoDB process to
access /sys/fs/cgroup
, which is required to determine
the available memory on your system. If you intend to run SELinux in
enforcing
mode, you will need to make the following adjustment
to your SELinux policy:
Ensure your system has the
checkpolicy
package installed:Create a custom policy file
mongodb_cgroup_memory.te
:Once created, compile and load the custom policy module by running these three commands:
The MongoDB process is now able to access the correct files with
SELinux set to enforcing
.
Important
You will also need to further customize your SELinux policy in the
following two cases if SELinux is in enforcing
mode:
- You are not using the default MongoDB directories (for RHEL 7.0), and/or
- You are not using default MongoDB ports.
Non-Default MongoDB Directory Path(s)¶
Update the SELinux policy to allow the
mongod
service to use the new directory:where specify one of the following types as appropriate:
mongod_var_lib_t
for data directorymongod_log_t
for log file directorymongod_var_run_t
for pid file directory
Note
Be sure to include the
.*
at the end of the directory.Update the SELinux user policy for the new directory:
where specify one of the following types as appropriate:
mongod_var_lib_t
for data directorymongod_log_t
for log directorymongod_var_run_t
for pid file directory
Apply the updated SELinux policies to the directory:
For examples:
Tip
- Depending on your user permission, you may need to use
sudo
to perform these operations. - Be sure to include the
.*
at the end of the directory for thesemanage fcontext
operations.
If using a non-default MongoDB data path of
/mongodb/data
:If using a non-default MongoDB log directory of
/mongodb/log
(e.g. if the log file path is/mongodb/log/mongod.log
):
Non-Default MongoDB Ports¶
Tip
Depending on your user permission, you may need to use sudo
to
perform the operation.
Optional. Suppress FTDC
Warnings¶
The current SELinux Policy does not allow the MongoDB process to open
and read /proc/net/netstat
for Diagnostic Parameters (FTDC). As such,
the audit log may include numerous messages regarding lack of access
to this path.
To track the proposed fix, see https://github.com/fedora-selinux/selinux-policy-contrib/pull/79.
Optionally, as a temporary fix, you can manually adjust the SELinux Policy:
Ensure your system has the
checkpolicy
package installed:Create a custom policy file
mongodb_proc_net.te
:Once created, compile and load the custom policy module by running these three commands:
Procedure¶
Create the data and log directories.¶
Note
Depending on user permissions, you may need to sudo mkdir -p
<directory>
instead of mkdir -p <directory>
. Use or omit
sudo
as appropriate. See your linux man pages for information
on mkdir
and sudo
.
Create a directory where the MongoDB instance stores its data. For example:
Create a directory where the MongoDB instance stores its log. For example:
The user that starts the MongoDB process must have read and write permission to these directories. For example, if you intend to run MongoDB as yourself:
Verify that MongoDB has started successfully.¶
Verify that MongoDB has started successfully by
checking the process output for the following line in the
log file /var/log/mongodb/mongod.log
:
You may see non-critical warnings in the process output. As long as you see the log line shown above, you can safely ignore these warnings during your initial evaluation of MongoDB.
Begin using MongoDB.¶
Start a mongo
shell on the same host machine as the
mongod
. You can run the mongo
shell
without any command-line options to connect to a
mongod
that is running on your localhost with default
port 27017:
For more information on connecting using the mongo
shell, such as to connect to a mongod
instance running
on a different host and/or port, see The mongo Shell.
To help you start using MongoDB, MongoDB provides Getting Started Guides in various driver editions. See Getting Started for the available editions.