Navigation

Install MongoDB Community using .tgz Tarball on SUSE

Overview

The following tutorial downloads the .tgz tarball directly to install MongoDB 4.2 Community Edition on SUSE Linux Enterprise Server (SLES) 12. Although the recommended procedure to install is through the package manager, you can also install by directly downloading the .tgz file.

Considerations

Note

SUSE Linux Enterprise Server and potentially other SUSE distributions ship with virtual memory address space limited to 8 GB by default. You must adjust this in order to prevent virtual memory allocation failures as the database grows.

The SLES packages for MongoDB automatically adjust these limits in their default init script. If you are starting MongoDB manually without the provided init script, are using your own custom init script, or are using the TGZ tarball release, you must make these changes yourself.

Platform Support

MongoDB supports SUSE Linux Enterprise Server (SLES) 12.

This installation guide only supports 64-bit systems. See Supported Platforms for more information.

Windows Subsystem for Linux (WSL) - Unsupported

MongoDB does not support WSL, and users on WSL have encountered various issues installing on WSL. For examples, see:

Production Notes

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

MongoDB Version

The following tutorial installs MongoDB 4.2 Community Edition.

To install a different version of MongoDB, please refer to that version’s documentation. For example, to install version 4.0, see the tutorial for version 4.0.

Prerequisites

MongoDB .tar.gz tarballs require installing the following dependencies:

zypper install libcurl4 libopenssl1_0_0

Tip

Depending on your user permission, you may need to use sudo to perform the operation.

Procedure

1

Download the MongoDB .tgz tarball.

Download the tarball for your system from the MongoDB Download Center.

2

Extract the files from the downloaded archive.

For example, from a system shell, you can extract using the tar command:

tar -zxvf mongodb-linux-*-4.2.1.tgz
3

Ensure the binaries are in a directory listed in your PATH environment variable.

The MongoDB binaries are in the bin/ directory of the tarball. You can either:

  • Copy the binaries into a directory listed in your PATH variable, such as /usr/local/bin (Update /path/to/the/mongodb-directory/ with your installation directory as appropriate)

    sudo cp /path/to/the/mongodb-directory/bin/* /usr/local/bin/
    
  • Create symbolic links to the binaries from a directory listed in your PATH variable, such as /usr/local/bin (Update /path/to/the/mongodb-directory/ with your installation directory as appropriate):

    sudo ln -s  /path/to/the/mongodb-directory/bin/* /usr/local/bin/
    

Run MongoDB

1

Create the data and log directories.

Note

Depending on user permissions, you may need to sudo mkdir -p <directory> instead of mkdir -p <directory>. Use or omit sudo as appropriate. See your linux man pages for information on mkdir and sudo.

Create a directory where the MongoDB instance stores its data. For example:

sudo mkdir -p /var/lib/mongo

Create a directory where the MongoDB instance stores its log. For example:

sudo mkdir -p /var/log/mongodb

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:

sudo chown `whoami` /var/lib/mongo     # Or substitute another user
sudo chown `whoami` /var/log/mongodb   # Or substitute another user
2

Run MongoDB.

To run MongoDB, run the mongod process at the system prompt.

mongod --dbpath /var/lib/mongo --logpath /var/log/mongodb/mongod.log --fork

For details on the command-line options --dbpath and --logpath, see Options.

3

Verify that MongoDB has started successfully.

Verify that MongoDB has started successfully by checking the process output for the following line in the log file /var/log/mongodb/mongod.log:

[initandlisten] waiting for connections on port 27017

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.

4

Begin using MongoDB.

Start a 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:

mongo

For more information on connecting using the mongo shell, such as to connect to a mongod instance running on a different host and/or port, see The mongo Shell.

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

For information on CRUD (Create,Read,Update,Delete) operations, see: