Install MongoDB Enterprise Edition on SUSE¶
MongoDB Atlas is a hosted MongoDB service option in the cloud which requires no installation overhead and offers a free tier to get started.
Use this tutorial to install MongoDB 4.4 Enterprise Edition
on SUSE Linux Enterprise Server (SLES) using the
MongoDB Enterprise Edition is available on select platforms and contains support for several features related to security and monitoring.
This tutorial installs MongoDB 4.4 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.
MongoDB 4.4 Enterprise Edition supports the following 64-bit SUSE Linux Enterprise Server (SLES) releases on x86_64 architecture:
- SLES 15
- SLES 12
MongoDB only supports the 64-bit versions of these platforms.
MongoDB 4.4 Enterprise Edition on SLES also supports the s390x architecture on select platforms.
See Supported Platforms for more information.
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.
Install MongoDB Enterprise Edition¶
Follow these steps to install MongoDB Enterprise Edition using the
zypper package manager.
Import the MongoDB public key.¶
sudo rpm --import https://www.mongodb.org/static/pgp/server-4.4.asc
Add the MongoDB repository.¶
Add the repository so that you can install MongoDB. Use the command appropriate for your version of SUSE:
sudo zypper addrepo --gpgcheck "https://repo.mongodb.com/zypper/suse/15/mongodb-enterprise/4.4/x86_64/" mongodb
Install the MongoDB packages.¶
To install MongoDB 4.4, issue the following command:
sudo zypper -n install mongodb-enterprise
To install a specific release of MongoDB, specify each component package individually and append the version number to the package name, as in the following example:
sudo zypper install mongodb-enterprise-4.4 mongodb-enterprise-server-4.4 mongodb-enterprise-shell-4.4 mongodb-enterprise-mongos-4.4 mongodb-enterprise-tools-4.4
You can specify any available version of MongoDB. However
upgrades the packages when a newer version becomes available. To
prevent unintended upgrades, pin the packages by running the following
sudo zypper addlock mongodb-enterprise-4.4 mongodb-enterprise-server-4.4 mongodb-enterprise-shell-4.4 mongodb-enterprise-mongos-4.4 mongodb-enterprise-tools-4.4
Previous versions of MongoDB packages use a different repository location. Refer to the version of the documentation appropriate for your MongoDB version.
Run MongoDB Enterprise Edition¶
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
directories to give this user access to these directories.
To specify a different log file directory and data file directory, edit
storage.dbPath settings in
/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
process may use. These limits may negatively impact MongoDB operation,
and should be adjusted. See UNIX
ulimit Settings for the recommended
settings for your platform.
Starting in MongoDB 4.4, a startup error is generated if the
ulimit value for number of open files is under
Follow these steps to run MongoDB Enterprise Edition. These instructions assume that you are using the default settings.
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
while older versions of Linux tend to use System V init (which uses
If you are unsure which init system your platform uses, run the following command:
ps --no-headers -o comm 1
Then 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
sudo systemctl start mongod
If you receive an error similar to the following when starting
Failed to start mongod.service: Unit mongod.service not found.
Run the following command first:
sudo systemctl daemon-reload
Then run the start command above again.
Verify that MongoDB has started successfully.¶
You can verify that the
mongod process has started
successfully by issuing the following command:
sudo systemctl status mongod
You can optionally ensure that MongoDB will start following a system reboot by issuing the following command:
sudo systemctl enable mongod
Begin using MongoDB.¶
mongo shell on the same host machine as the
mongod. You can run the
without any command-line options to connect to a
mongod that is running on your localhost with default
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.
This 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.
Remove any MongoDB packages that you had previously installed.
sudo zypper remove $(rpm -qa | grep mongodb-enterprise)
Remove Data Directories.¶
Remove MongoDB databases and log files.
sudo rm -r /var/log/mongodb sudo rm -r /var/lib/mongo
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
not be able to initialize a replica set unless this value is set
to a valid network interface.
This value can be configured either:
MongoDB Enterprise Edition Packages¶
MongoDB Enterprise Edition is available from its own dedicated repository, and contains the following officially-supported packages:
Contains the mongocryptd binary