This version of the documentation is archived and no longer supported.

Install MongoDB Enterprise on SUSE


Use this tutorial to install MongoDB Enterprise on SUSE Linux. MongoDB Enterprise is available on select platforms and contains support for several features related to security and monitoring.

Platform Support

This installation guide only supports 64-bit systems. See Platform Support for details.


MongoDB provides officially supported Enterprise packages in their own repository. This repository contains the following packages:

Init Scripts

The mongodb-enterprise package includes various init scripts, including the init script /etc/rc.d/init.d/mongod.

The package configures MongoDB using the /etc/mongod.conf file in conjunction with the init scripts. See the Configuration File reference for documentation of settings available in the configuration file.

As of version 3.0.15, there are no init scripts for mongos. The mongos process is used only in sharding. You can use the mongod init script to derive your own mongos init script.


MongoDB only provides Enterprise packages for 64-bit builds of SUSE Enterprise Linux version 11.

Use the provided distribution packages as described in this page if possible. These packages will automatically install all of MongoDB’s dependencies, and are the recommended installation method.


SUSE Linux Enterprise Server 11 and potentially other versions of SLES and other SUSE distributions ship with virtual memory address space limited to 8GB by default. This must be adjusted in order to prevent virtual memory allocation failures as the database grows.

The SLES packages for MongoDB adjust these limits in the default scripts, but you will need to make this change manually if you are using custom scripts and/or the tarball release rather than the SLES packages.

Install MongoDB Enterprise


Configure the package management system (zypper).

Add the repository so that you can install MongoDB using zypper.

Use the following command to specify the 3.0 release of MongoDB.

sudo zypper addrepo --no-gpgcheck mongodb

If you’d like to install MongoDB packages from a previous release series, such as 2.6, you can specify the release series in the repository configuration. For example, to restrict your system to the 2.6 release series, use the following command:

sudo zypper addrepo --no-gpgcheck mongodb

Install the MongoDB packages and associated tools.

When you install the packages, you choose whether to install the current release or a previous one. This step provides the commands for both.

To install the 3.0 release of MongoDB, 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-3.0.15 mongodb-enterprise-server-3.0.15 mongodb-enterprise-shell-3.0.15 mongodb-enterprise-mongos-3.0.15 mongodb-enterprise-tools-3.0.15

You can specify any available version of MongoDB. However zypper will upgrade 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-3.0.15 mongodb-enterprise-server-3.0.15 mongodb-enterprise-shell-3.0.15 mongodb-enterprise-mongos-3.0.15 mongodb-enterprise-tools-3.0.15

Previous versions of MongoDB packages use a different repository location. Refer to the version of the documentation appropriate for your MongoDB version.

Install MongoDB Enterprise From Tarball

While you should use the .rpm packages as previously described, you may also manually install MongoDB using the tarballs.

First you must install any dependencies as appropriate:

zypper install cyrus-sasl cyrus-sasl-plain cyrus-sasl-gssapi krb5 \
           libopenssl0_9_8 net-snmp libstdc++46 zlib

To perform the installation, see Install MongoDB Enterprise From Tarball.

Run MongoDB Enterprise


The MongoDB instance stores its data files in /var/lib/mongo and its log files in /var/log/mongodb by default, and runs using the mongod user account. You can specify alternate log and data file directories in /etc/mongod.conf. See systemLog.path and storage.dbPath for additional information.

If you change the user that runs the MongoDB process, you must modify the access control rights to the /var/lib/mongo and /var/log/mongodb directories to give this user access to these directories.



Start MongoDB.

You can start the mongod process by issuing the following command:

sudo service mongod start

Verify 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 on

Stop MongoDB.

As needed, you can stop the mongod process by issuing the following command:

sudo service mongod stop

Restart MongoDB.

You can restart the mongod process by issuing the following command:

sudo service mongod restart

You 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.

To help you start using MongoDB, MongoDB provides Getting Started Guides in various driver editions. See Getting Started for the available editions.

Before deploying MongoDB in a production environment, consider the Production Notes document.

Later, to stop MongoDB, press Control+C in the terminal where the mongod instance is running.

Uninstall MongoDB

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.


Stop MongoDB.

Stop the mongod process by issuing the following command:

sudo service mongod stop

Remove Packages.

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