Overview
Use this tutorial to install MongoDB 9.0 Enterprise Edition on SUSE Linux Enterprise Server (SLES) using the ZYpp package manager.
MongoDB Enterprise Edition is available on select platforms and contains support for features related to security and monitoring.
MongoDB Version
This tutorial installs MongoDB 9.0 Enterprise Edition. To install a different version of MongoDB Enterprise, use the version drop-down menu in the sidebar and select the documentation for that version.
Considerations
Platform Support
MongoDB 9.0 Enterprise Edition supports the following 64-bit SUSE Linux Enterprise Server (SLES) releases on x86_64 architecture:
SLES 15
SLES 16
MongoDB only supports the 64-bit versions of these platforms.
See Platform Support for more information.
Production Notes
Before deploying MongoDB in a production environment, see the Production Notes for Self-Managed Deployments document for performance considerations and configuration recommendations.
Install MongoDB Enterprise Edition
Follow these steps to install MongoDB Enterprise Edition using the ZYpp package manager.
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/16/mongodb-enterprise/9.0/x86_64/" mongodbsudo zypper addrepo --gpgcheck "https://repo.mongodb.com/zypper/suse/15/mongodb-enterprise/9.0/x86_64/" mongodbInstall the MongoDB packages.
To install MongoDB 9.0, issue the following command:
sudo zypper -n install mongodb-enterpriseTo 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-9.0.4 mongodb-enterprise-database-9.0.4 mongodb-enterprise-server-9.0.4 mongodb-mongosh mongodb-enterprise-mongos-9.0.4 mongodb-enterprise-tools-9.0.4You can specify any available version of MongoDB. However zypper upgrades the packages when a newer version becomes available. To prevent unintended upgrades, pin the packages by running the following command:
sudo zypper addlock mongodb-enterprise-9.0.4 mongodb-enterprise-database-9.0.4 mongodb-enterprise-server-9.0.4 mongodb-mongosh mongodb-enterprise-mongos-9.0.4 mongodb-enterprise-tools-9.0.4Previous 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, a MongoDB instance stores:
its data files in
/var/lib/mongoits log files in
/var/log/mongodb
If you installed using the package manager, these default directories are created during installation.
If you installed manually by downloading the tarballs, 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 mkdir and sudo.
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/lib/mongo and /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 systemLog.path and 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 process may use. These limits may negatively impact MongoDB operation, and should be adjusted. See UNIX ulimit Settings for Self-Managed Deployments for the recommended settings for your platform.
Note
If the ulimit value for number of open files is under 64000, MongoDB generates a startup warning.
Procedure
Follow these steps to run MongoDB Enterprise Edition. These instructions assume that you are using the default settings.
Init System
To run and manage your mongod process, use your operating system's built-in init system. Recent versions of Linux use systemd, which uses the systemctl command, while older versions of Linux use System V init, which uses the service command.
If you are unsure which init system your platform uses, run the following command:
ps --no-headers -o comm 1Then 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.
Start MongoDB.
You can start the mongod process by issuing the following command:
sudo systemctl start mongodIf you receive an error similar to the following when starting mongod:
Failed to start mongod.service: Unit mongod.service not found.
Run the following command first:
sudo systemctl daemon-reloadThen 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 mongodYou can optionally ensure that MongoDB will start following a system reboot by issuing the following command:
sudo systemctl enable mongodStop MongoDB.
As needed, you can stop the mongod process by issuing the following command:
sudo systemctl stop mongodRestart MongoDB.
You can restart the mongod process by issuing the following command:
sudo systemctl restart mongodYou can follow the state of the process for errors or important messages by watching the output in the /var/log/mongodb/mongod.log file.
Begin using MongoDB.
Start a mongosh session on the same host machine as the mongod. You can run mongosh without any command-line options to connect to a mongod that is running on your localhost with default port 27017.
mongoshFor more information on connecting using mongosh, such as to connect to a mongod instance running on a different host and/or port, see the mongosh documentation.
To help you start using MongoDB, MongoDB provides Getting Started Guides in various driver editions. For the driver documentation, see Start Developing with MongoDB.
Start MongoDB.
You can start the mongod process by issuing the following command:
sudo service mongod startVerify that MongoDB has started successfully
You can verify that the mongod process has started successfully by checking the contents of the log file at /var/log/mongodb/mongod.log for a line reading
[initandlisten] waiting for connections on port <port>where <port> is the port configured in /etc/mongod.conf, 27017 by default.
You can optionally ensure that MongoDB will start following a system reboot by issuing the following command:
sudo chkconfig mongod onStop MongoDB.
As needed, you can stop the mongod process by issuing the following command:
sudo service mongod stopRestart MongoDB.
You can restart the mongod process by issuing the following command:
sudo service mongod restartYou can follow the state of the process for errors or important messages by watching the output in the /var/log/mongodb/mongod.log file.
Begin using MongoDB.
Start a mongosh session on the same host machine as the mongod. You can run mongosh without any command-line options to connect to a mongod that is running on your localhost with default port 27017.
mongoshFor more information on connecting using mongosh, such as to connect to a mongod instance running on a different host and/or port, see the mongosh documentation.
To help you start using MongoDB, MongoDB provides Getting Started Guides in various driver editions. For the driver documentation, see Start Developing with MongoDB.
Additional Information
Localhost Binding by Default
By default, MongoDB launches with bindIp set to 127.0.0.1, which binds it to the localhost network interface. This means that the mongod instance only accepts connections from clients running on the same machine. To allow remote clients to access the mongod instance or to initialize a replica set on the instance, you must bind mongod to a publicly-accessible network interface.
To bind the network interface, use the bindIp setting in the configuration file or start mongod with the --bind_ip command-line option.
Warning
Before you bind your instance to a publicly-accessible IP address, you must secure your cluster from unauthorized access. For a complete list of security recommendations, see Security Checklist for Self-Managed Deployments. At minimum, consider enabling authentication and hardening network infrastructure.
For more information on configuring bindIp, see IP Binding in Self-Managed Deployments.
MongoDB Enterprise Edition Packages
MongoDB Enterprise Edition is available from its own dedicated repository, and contains the following officially-supported packages:
Package Name | Description |
|---|---|
| A |
| A
|
| Contains the MongoDB Shell ( |
| Contains the MongoDB Shell that uses the OpenSSL version already installed on your computer ( |
| A
|