Install MongoDB Enterprise on SUSE using .tgz Tarball
On this page
Use this tutorial to manually install MongoDB 3.6 Enterprise Edition on SUSE Linux Enterprise Server (SLES) 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
zypper 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 zypper Package Manager for instructions.
MongoDB 3.6 Enterprise Edition supports the following 64-bit SUSE Linux Enterprise Server (SLES) release on x86_64 architecture:
- SLES 12 - for MongoDB versions 3.6.0 - 3.6.16 only. More recent version of MongoDB 3.6 are not supported on SLES 12. Please consider upgrading to MongoDB 4.0 or later.
MongoDB only supports the 64-bit version of this platform.
See Supported Platforms for more information.
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
- Version 7
- Version 8
Follow these steps to manually install MongoDB Enterprise Edition from the
After you have installed the required prerequisite packages, download the MongoDB Enterprise tarball for your system from the MongoDB Download Center .
The MongoDB binaries are in the
bin/ directory of the tarball. You can either:
Copy the binaries into a directory listed in your
PATHvariable, such as
/path/to/the/mongodb-directory/with your installation directory as appropriate)
Create symbolic links to the binaries from a directory listed in your
PATHvariable, such as
/path/to/the/mongodb-directory/with your installation directory as appropriate):
By default, MongoDB instance stores:
- its data files in
- its log files in
If you installed via the package manager, these default directories are created during the installation.
If you installed manually by downloading the tarballs, you can create the directories using
mkdir -p <directory> or
sudo mkdir -p <directory> depending on the user that will run MongoDB. (See your linux man pages for information on
By default, MongoDB runs using the
mongod user account. If you change the user that runs the MongoDB process, you must also modify the permission to the
/var/log/mongodb directories to give this user access to these directories.
To specify a different log file directory and data file directory, edit the
storage.dbPath settings in the
/etc/mongod.conf. Ensure that the user running MongoDB has access to these directories.
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.
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:
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 by checking the process output for the following line in the log file
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.
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: