Navigation

Install MongoDB Community Edition on SUSE

On this page

Overview

Use this tutorial to install MongoDB 3.6 Community Edition on SUSE Linux Enterprise Server (SLES) using the zypper package manager.

MongoDB Version

This tutorial installs MongoDB 3.6 Community Edition. To install a different version of MongoDB Community, use the version drop-down menu in the upper-left corner of this page to select the documentation for that version.

Considerations

Platform Support

MongoDB 3.6 Community Edition supports the following 64-bit SUSE Linux Enterprise Server (SLES) release on x86_64 architecture:

  • SLES 12

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

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 Community Edition

Follow these steps to install MongoDB Community Edition using the zypper package manager.

1

Import the MongoDB public key

copy 
sudo rpm --import https://www.mongodb.org/static/pgp/server-3.6.asc
2

Configure the package management system (zypper).

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

Changed in version 3.0: MongoDB Linux packages are in a new repository beginning with 3.0.

For MongoDB 3.6

Run the command appropriate for your version of SUSE:

SUSE 12
copy 
sudo zypper addrepo --gpgcheck "https://repo.mongodb.org/zypper/suse/12/mongodb-org/3.6/x86_64/" mongodb

For versions of MongoDB earlier than 3.6

To install MongoDB packages from a previous release series such as 3.4, you can specify the release series in the repository configuration.

For example, to restrict your SUSE 12 system to the 3.4 release series, use the following command:

copy 
sudo zypper addrepo --no-gpgcheck https://repo.mongodb.org/zypper/suse/12/mongodb-org/3.4/x86_64/ mongodb
3

Install the MongoDB packages.

To install the latest stable version of MongoDB, issue the following command:

copy 
sudo zypper -n install mongodb-org

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:

copy 
sudo zypper install mongodb-org-3.6.17 mongodb-org-server-3.6.17 mongodb-org-shell-3.6.17 mongodb-org-mongos-3.6.17 mongodb-org-tools-3.6.17

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:

copy 
sudo zypper addlock mongodb-org-3.6.17 mongodb-org-server-3.6.17 mongodb-org-shell-3.6.17 mongodb-org-mongos-3.6.17 mongodb-org-tools-3.6.17

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

Run MongoDB Community 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.
Directories

By default, MongoDB instance stores:

  • its data files in /var/lib/mongo
  • its log files in /var/log/mongodb

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

Procedure

Follow these steps to run MongoDB Community 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 initialization system. Recent versions of Linux tend to use systemd (which uses the systemctl command), while older versions of Linux tend to use System V init (which uses the service command). Refer to the documentation for your operating system for more information.

Use the initialization system appropriate for your platform:

1

Start MongoDB.

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

copy 
sudo systemctl start mongod

If 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:

copy 
sudo systemctl daemon-reload

Then run the start command above again.

2

Verify that MongoDB has started successfully.

You can verify that the mongod process has started successfully by issuing the following command:

copy 
sudo systemctl status mongod

You can optionally ensure that MongoDB will start following a system reboot by issuing the following command:

copy 
sudo systemctl enable mongod
3

Stop MongoDB.

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

copy 
sudo systemctl stop mongod
4

Restart MongoDB.

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

copy 
sudo systemctl restart mongod

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.

5

Begin using MongoDB.

Start a mongo shell on the same host machine as the mongod. Use the --host command line option to specify the localhost address and port that the mongod listens on:

copy 
mongo --host 127.0.0.1:27017

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

1

Start MongoDB.

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

copy 
sudo service mongod start
2

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

copy 
[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:

copy 
sudo chkconfig mongod on
3

Stop MongoDB.

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

copy 
sudo service mongod stop
4

Restart MongoDB.

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

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

5

Begin using MongoDB.

Start a mongo shell on the same host machine as the mongod. Use the --host command line option to specify the localhost address and port that the mongod listens on:

copy 
mongo --host 127.0.0.1:27017

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

Uninstall MongoDB Community Edition

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.

Warning

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.

1

Stop MongoDB.

Stop the mongod process by issuing the following command:

copy 
sudo service mongod stop
2

Remove Packages.

Remove any MongoDB packages that you had previously installed.

copy 
sudo zypper remove $(rpm -qa | grep mongodb-org)
3

Remove Data Directories.

Remove MongoDB databases and log files.

copy 
sudo rm -r /var/log/mongodb
sudo rm -r /var/lib/mongo

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:

  • in the MongoDB configuration file with bindIp, or
  • via the command-line argument --bind_ip

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.

MongoDB Community Edition Packages

MongoDB Community Edition is available from its own dedicated repository, and contains the following officially-supported packages:

Package Name Description
mongodb-org A metapackage that will automatically install the four component packages listed below.
mongodb-org-server Contains the mongod daemon and associated configuration and init scripts.
mongodb-org-mongos Contains the mongos daemon.
mongodb-org-shell Contains the mongo shell.
mongodb-org-tools Contains the following MongoDB tools: mongoimport bsondump, mongodump, mongoexport, mongofiles, mongoperf, mongorestore, mongostat, and mongotop.

The mongodb-org-server package provides an initialization script that starts mongod with the /etc/mongod.conf configuration file.

See Run MongoDB Community Edition for details on using this initialization script.

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.