Install MongoDB Enterprise on Ubuntu using .tgz Tarball
On this page
Use this tutorial to manually install MongoDB 3.6 Enterprise Edition on LTS (long-term support) releases of Ubuntu Linux using a downloaded
MongoDB Enterprise Edition is available on select platforms and contains support for several features related to security and monitoring.
This tutorial installs MongoDB 3.6 Enterprise Edition. To install a different version of MongoDB Enterprise, use the version drop-down menu in the upper-left corner of this page to select the documentation for that version.
While MongoDB can be installed manually via a downloaded
.tgz tarball as described in this document, it is recommended to use the
apt package manager on your system to install MongoDB if possible. Using a package manager automatically installs all needed dependencies, provides an example
mongod.conf file to get you started, and simplifies future upgrade and maintenance tasks.
➤ See Install MongoDB using the apt Package Manager for instructions.
MongoDB 3.6.4 Enterprise Edition removes support for Ubuntu 12.04 (“Precise”) on x86_64
MongoDB 3.6.13 Enterprise Edition removes support for Ubuntu 16.04 (“Xenial”) on PPC64LE
MongoDB 3.6.5 Enterprise Edition removes support for Ubuntu 16.04 (“Xenial”) on s390x
MongoDB 3.6 Enterprise Edition supports the following 64-bit Ubuntu LTS (long-term support) releases on x86_64 architecture:
16.04 LTS (“Xenial”)
14.04 LTS (“Trusty”)
MongoDB only supports the 64-bit versions of these platforms.
MongoDB 3.6 Enterprise Edition on Ubuntu also supports the ARM64 architecture on select platforms.
See Supported Platforms for more information.
For earlier MongODB Enterprise versions that support Ubuntu 16.04 POWER/PPC64LE:
Due to a lock elision bug present in older versions of the
glibc package on Ubuntu 16.04 for POWER, you must upgrade the
glibc package to at least
glibc 2.23-0ubuntu5 before running MongoDB. Systems with older versions of the
glibc package will experience database server crashes and misbehavior due to random memory corruption, and are unsuitable for production deployments of MongoDB
Windows Subsystem for Linux (WSL) - Unsupported
MongoDB does not support the Windows Subsystem for Linux (WSL).
Before deploying MongoDB in a production environment, consider the Production Notes document which offers performance considerations and configuration recommendations for production MongoDB deployments.
Use the following command to install the dependencies required for the MongoDB Enterprise
sudo apt-get install libcurl3 libgssapi-krb5-2 libkrb5-dbg libldap-2.4-2 libpci3 libwrap0 libsasl2-2 libsensors4 snmp openssl
sudo apt-get install libcurl3 libgssapi-krb5-2 libkrb5-dbg libldap-2.4-2 libwrap0 libsasl2-2 libsensors4 snmp openssl
Follow these steps to manually install MongoDB Enterprise Edition from the
Download the tarball for your system from the MongoDB Download Center.
Using an archive manager program or the
tar command, extract the files.
For example, to extract from the terminal shell, you can use the following
If you downloaded a different MongoDB 3.6 point release, be sure to modify the command to reflect the correct
.tgz file name.
tar -zxvf mongodb-linux-*-3.6.19.tgz
The MongoDB binaries are in the
To avoid having to specify the path to the MongoDB binaries, you can copy these binaries into a directory listed in your
PATH variable such as
sudo cp <mongodb-install-directory>/bin/* /usr/local/bin/
- Most Unix-like operating systems limit the system resources that a session may use. These limits may negatively impact MongoDB operation. See UNIX ulimit Settings for more information.
- You can configure the MongoDB instance (such as the data directory and log directory specifications) using either the command-line options or a configuration file.
Follow these steps to run MongoDB Enterprise Edition. These instructions assume that you are using the default settings.
Create a directory where the MongoDB instance stores its data. For example:
sudo mkdir -p /var/lib/mongo
Create a directory where the MongoDB instance stores its log. For example:
sudo mkdir -p /var/log/mongodb
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:
sudo chown `whoami` /var/lib/mongo # Or substitute another user sudo chown `whoami` /var/log/mongodb # Or substitute another user
To run MongoDB, run the mongod process at the system prompt.
mongod --dbpath /var/lib/mongo --logpath /var/log/mongodb/mongod.log --fork
Verify that MongoDB has started successfully by checking the process output for the following line in the log file
[initandlisten] waiting for connections on port 27017
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.
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:
By 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: