- Install MongoDB >
- Install MongoDB Enterprise >
- Install MongoDB Enterprise on Linux >
- Install MongoDB Enterprise Edition on Ubuntu >
- Install MongoDB Enterprise on Ubuntu using .tgz Tarball
Install MongoDB Enterprise on Ubuntu using .tgz Tarball¶
On this page
Overview¶
Use this tutorial to manually install MongoDB 3.6 Enterprise
Edition on LTS (long-term support) releases of Ubuntu Linux using a
downloaded .tgz
tarball.
MongoDB Enterprise Edition is available on select platforms and contains support for several features related to security and monitoring.
MongoDB Version¶
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.
Installation Method¶
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.
Considerations¶
Platform Support¶
EOL Notice
MongoDB 3.6 Enterprise Edition supports the following 64-bit Ubuntu LTS (long-term support) releases on x86_64 architecture:
- 18.04 LTS (“Bionic”) (Starting in MongoDB Enterprise 3.6.20)
- 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.
Note
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).
Production Notes¶
Before deploying MongoDB in a production environment, consider the Production Notes document which offers performance considerations and configuration recommendations for production MongoDB deployments.
Install MongoDB Enterprise Edition¶
Prerequisites¶
Use the following command to install the dependencies required for the
MongoDB Enterprise .tgz
tarball:
- Ubuntu 18.04 (Bionic)
- Ubuntu 16.04 (Xenial)
- Ubuntu 14.04 (Trusty)
Procedure¶
Follow these steps to manually install MongoDB Enterprise Edition from
the .tgz
.
Download the MongoDB .tgz
tarball.¶
Download the tarball for your system from the MongoDB Download Center.
Extract the files from the downloaded archive.¶
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 tar
command:
Tip
If you downloaded a different MongoDB 3.6 point release,
be sure to modify the command to reflect the correct .tgz
file name.
Optional. Ensure the binaries are in a directory listed in your PATH
environment variable.¶
The MongoDB binaries are in the <mongodb-install-directory>/bin/
directory.
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 /usr/local/bin
:
Run MongoDB Enterprise Edition¶
- ulimit Considerations
- 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.
- Configuration
- 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.
Procedure¶
Follow these steps to run MongoDB Enterprise Edition. These instructions assume that you are using the default settings.
Create the data and log directories.¶
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.
Additional Information¶
Localhost Binding by Default¶
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:
Warning
Before binding to a non-localhost (e.g. publicly accessible) IP address, ensure you have secured your cluster from unauthorized access. For a complete list of security recommendations, see Security Checklist. At minimum, consider enabling authentication and hardening network infrastructure.
For more information on configuring bindIp
, see
MongoDB Configuration Hardening.