Start MongoDB Community Edition as a Windows Service¶ To start/restart the MongoDB service, use the Services console: From the Services console, locate the MongoDB service. Right-click on the MongoDB service and click Start. To begin using MongoDB, connect a mongo.exe shell to the running MongoDB. Brew tap mongodb/brew Then install Mongo: brew install mongodb-community@4.0 To run from the command line in the foreground. Sudo systemctl start mongodb sudo systemctl restart mongodb By default Mongo is setup to run automatically. To disable/enable this behavior.

1. When To Use Mongodb
2. Brew Services Start Mongodb-community 4.4
3. Brew Start Mongodb Free
4. Brew Start Mongodb 2020
5. Brew Install Mongodb
6. Brew Start Mongodb Error

The command line and configurationfile interfaces provide MongoDBadministrators with a large number of options and settings forcontrolling the operation of the database system. This documentprovides an overview of common configurations and examples ofbest-practice configurations for common use cases.

While both interfaces provide access to the same collection of optionsand settings, this document primarily uses the configuration fileinterface.

• If you installed MongoDB with a package managersuch as yum or apt on Linux or brew on macOS, or with theMSI installer on Windows, a default configuration file has been provided as part of yourinstallation:

  Method
  Linux	/etc/mongod.conf
  brew Package Manager	/usr/local/etc/mongod.conf (on Intel processors), or /opt/homebrew/etc/mongod.conf (on Apple M1 processors)
  MSI Installer

• If you installed MongoDB via a downloadedTGZ or ZIP file, you will need to create your own configurationfile. The basic example configuration is a goodplace to start.

For package installations of MongoDB on Linux or macOS, aninitialization script which uses this default configuration file is alsoprovided. This initialization script can be used to start themongod on these platforms in the following manner:

• On Linux systems that use the systemd init system (thesystemctl command):

• On Linux systems that use the SystemV init init system (theservice command):

• On macOS, using the brew package manger:

If you installed MongoDB using a TGZ or ZIP file, you will needto create your own configuration file. Abasic example configuration can be found later inthis document. Once you have created a configuration file, you can starta MongoDB instance with this configuration file by using either the--config or -foptions to mongod. For example, on Linux:

Modify the values in the mongod.conf file on your system tocontrol the configuration of your database instance.

Configure the Database¶

Consider the following basic configuration:

For most standalone servers, this is a sufficient baseconfiguration. It makes several assumptions, but consider thefollowing explanation:

• fork is true, which enables adaemon mode for mongod, which detaches (i.e. 'forks')the MongoDB from the current session and allows you to run thedatabase as a conventional server.

• bindIp is localhost, which forces theserver to only listen for requests on the localhost IP. Only bind tosecure interfaces that the application-level systems can access withaccess control provided by system network filtering(i.e. 'firewall').

• port is 27017, which is the defaultMongoDB port for database instances. MongoDB can bind to anyport. You can also filter access based on port using networkfiltering tools.

  UNIX-like systems require superuser privileges to attach processesto ports lower than 1024.

• quiet is true. This disables all butthe most critical entries in output/log file, and is notrecommended for production systems. If you do set this option, youcan use setParameter to modify this setting duringrun time.

• dbPath is /var/lib/mongo, whichspecifies where MongoDB will store its data files.

  If you installed MongoDB on Linux using a package manager,such as yum or apt, the /etc/mongod.conf file providedwith your MongoDB installation sets the following default dbPath,depending on your Linux distro:

  Package Manager
  RHEL / CentOS and Amazon	/var/lib/mongo
  zypper
  Ubuntu and Debian	/var/lib/mongodb
  brew

  The user account thatmongod runs under will need read and write access tothis directory.

• systemLog.path is /var/log/mongodb/mongod.logwhich is where mongod will write its output. If you do not setthis value, mongod writes all output to standard output(e.g. stdout.)
• logAppend is true, which ensures thatmongod does not overwrite an existing log filefollowing the server start operation.
• storage.journal.enabled is true, which enablesjournaling. Journaling ensures single instancewrite-durability. 64-bit builds of mongod enablejournaling by default. Thus, this setting may be redundant.

Given the default configuration, some of these values may beredundant. However, in many situations explicitly stating theconfiguration increases overall system intelligibility.

Security Considerations¶

The following configuration options are useful for limiting access to amongod instance:

This example provides four values to the bindIpoption:

• localhost, the localhost interface;
• 10.8.0.10, a private IP address typically used for localnetworks and VPN interfaces;
• 192.168.4.24, a private network interface typically used forlocal networks; and
• /tmp/mongod.sock, a Unix domain socket path.

Because production MongoDB instances need to be accessible frommultiple database servers, it is important to bind MongoDB tomultiple interfaces that are accessible from your applicationservers. At the same time it's important to limit these interfacesto interfaces controlled and protected at the network layer.

Replication and Sharding Configuration¶

Replication Configuration¶

replica set configuration is straightforward, and onlyrequires that the replSetName have a value that is consistentamong all members of the set. Consider the following:

Use descriptive names for sets. Once configured, use themongo shell to add hosts to the replica set.

To enable authentication for the replica set usingkeyfiles , add the followingkeyFile option [1]:

Setting keyFile enables authentication andspecifies a keyfile for the replica set member to use whenauthenticating to each other.

The Replica Set Security section forinformation on configuring authentication with replica sets.

The Replication document for more informationon replication in MongoDB and replica set configuration in general.

Sharding Configuration¶

Sharding requires mongod instances with differentmongod configurations for the config servers and the shards. The config servers store the cluster'smetadata, while the shards store the data.

To configure the config server mongod instances, in theconfiguration file, specify configsvr for thesharding.clusterRole setting.

Changed in version 3.4: Starting in version 3.4, MongoDB removes support for mirroredconfig servers and config servers must bedeployed as a replica set.

To deploy config servers as a replica set, the config servers must runthe WiredTiger Storage Engine. Initiate thereplica set and add members.

To configure the shard mongod instances, specifyshardsvr for the sharding.clusterRole setting, and ifrunning as a replica set, the replica set name:

If running as a replica set, initiate theshard replica set and add members.

For the router (i.e. mongos), configure at least onemongos process with the following setting:

You can specify additional members of the config server replica set byspecifying hostnames and ports in the form of a comma separated listafter the replica set name.

The Sharding section of the manual for moreinformation on sharding and cluster configuration.

Run Multiple Database Instances on the Same System¶

In many cases running multiple instances of mongod on asingle system is not recommended. On some types of deployments[2] and for testing purposes you may need to run more thanone mongod on a single system.

In these cases, use a base configuration for eachinstance, but consider the following configuration values:

The dbPath value controls the location of themongod instance's data directory. Ensure that each databasehas a distinct and well labeled data directory. ThepidFilePath controls where mongod processplaces it's process id (PID) file. As this tracks the specificmongod file, it is crucial that file be unique and welllabeled to make it easy to start and stop these processes.

Create additional init scripts and/oradjust your existing MongoDB configuration and init script asneeded to control these processes.

Diagnostic Configurations¶

The following configuration options control various mongodbehaviors for diagnostic purposes:

• operationProfiling.mode sets the database profiler level. The profiler is not active by defaultbecause of the possible impact on the profiler itself on performance.Unless this setting is on, queries are not profiled.
• operationProfiling.slowOpThresholdMs configures thethreshold which determines whether a query is 'slow' for thepurpose of the logging system and the profiler. The default value is 100 milliseconds. Setto a lower value if the logging system and the database profiler donot return useful results or set to a higher value to only log thelongest running queries.

  Starting in version 4.2 (also available starting in 4.0.6), secondary members of a replica set nowlog oplog entries that take longer than the slowoperation threshold to apply. These slow oplog messages are loggedfor the secondaries in the diagnostic log under the REPL component with the text appliedop: <oplog entry> took <num>ms. These slow oplog entries dependonly on the slow operation threshold. They do not depend on the loglevels (either at the system or component level), or the profilinglevel, or the slow operation sample rate. The profiler does notcapture slow oplog entries.

• systemLog.verbosity controls the amount of logging output thatmongod write to the log. Only use this option if you areexperiencing an issue that is not reflected in the normal logginglevel.

  Starting in MongoDB 3.0, you can also specify verbosity level forspecific components using thesystemLog.component.<name>.verbosity setting. For the availablecomponents, see component verbosity settings.

For more information, see also Database Profiling andMongoDB Performance.

When To Use Mongodb

MongoDB Atlasis a hosted MongoDB service option in the cloud which requires noinstallation overhead and offers a free tier to get started.

Overview¶

Use this tutorial to install MongoDB 4.4 Community Edition onLTS (long-term support) releases of Ubuntu Linux using theapt package manager.

MongoDB Version¶

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

Considerations¶

Platform Support¶

MongoDB 4.4 Community Edition supports the following64-bit Ubuntu LTS (long-term support) releases onx86_64 architecture:

• 20.04 LTS ('Focal')
• 18.04 LTS ('Bionic')
• 16.04 LTS ('Xenial')

MongoDB only supports the 64-bit versions of these platforms.

MongoDB 4.4 Community Edition on Ubuntu also supports theARM64 ands390x architectures onselect platforms.

See Supported Platforms for more information.

MongoDB does not support the Windows Subsystem for Linux (WSL).

Production Notes¶

Before deploying MongoDB in a production environment, consider theProduction Notes document which offersperformance considerations and configuration recommendations forproduction MongoDB deployments.

Official MongoDB Packages¶

To install MongoDB Community on your Ubuntu system, theseinstructions will use the official mongodb-org package, which ismaintained and supported by MongoDB Inc. The official mongodb-orgpackage always contains the latest version of MongoDB, and is availablefrom its own dedicated repo.

The mongodb package provided by Ubuntu is notmaintained by MongoDB Inc. and conflicts with the officialmongodb-org package. If you have already installed the mongodbpackage on your Ubuntu system, you must first uninstallthe mongodb package before proceeding with these instructions.

See MongoDB Community Edition Packages for the complete list of officialpackages.

Install MongoDB Community Edition¶

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

Import the public key used by the package management system.¶

From a terminal, issue the following command to import theMongoDB public GPG Key from https://www.mongodb.org/static/pgp/server-4.4.asc:

The operation should respond with an OK.

However, if you receive an error indicating that gnupg is notinstalled, you can:

1. Install gnupg and its required libraries using the following command:

2. Once installed, retry importing the key:

Create a list file for MongoDB.¶

Create the list file/etc/apt/sources.list.d/mongodb-org-4.4.list for yourversion of Ubuntu.

Click on the appropriate tab for your version of Ubuntu.If you are unsure of what Ubuntu version the host is running,open a terminal or shell on the host and execute lsb_release -dc.

The following instruction is for Ubuntu 20.04 (Focal).

Create the/etc/apt/sources.list.d/mongodb-org-4.4.listfile for Ubuntu 20.04 (Focal): Quicktime player download mac os x.

Reload local package database.¶

Issue the following command to reload the local package database:

Install the MongoDB packages.¶

You can install either the latest stable version of MongoDB or aspecific version of MongoDB.

To install the latest stable version, issue the following

Optional. Although you can specify any available version of MongoDB,apt-get will upgrade the packages when a newer version becomesavailable. To prevent unintended upgrades, you can pin the packageat the currently installed version:

For help with troubleshooting errors encountered while installingMongoDB on Ubuntu, see ourtroubleshooting guide.

Run MongoDB Community Edition¶

If you installed via the package manager, the data directory/var/lib/mongodb and the log directory /var/log/mongodb arecreated during the installation.

By default, MongoDB runs using the mongodb user account. Ifyou change the user that runs the MongoDB process, you must alsomodify the permission to the data and log directories to give thisuser access to these directories.

Procedure¶

Follow these steps to run MongoDB Community Edition on your system.These instructions assume that you are using the official mongodb-orgpackage -- not the unofficial mongodb package provided byUbuntu -- and are using the default settings.

Init System

To run and manage your mongod process, you will be usingyour operating system's built-in init system. Recent versions ofLinux tend to use systemd (which uses the systemctl command),while older versions of Linux tend to use System V init (which usesthe service command).

If you are unsure which init system your platform uses, run thefollowing command:

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.

Brew Services Start Mongodb-community 4.4

Start MongoDB.¶

You can start the mongod process by issuing thefollowing command:

If you receive an error similar to the following when startingmongod:

Failed to start mongod.service: Unit mongod.service not found.

Run the following command first:

Then run the start command above again.

Verify that MongoDB has started successfully.¶

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

Stop MongoDB.¶

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

Restart MongoDB.¶

You can restart the mongod process by issuing the followingcommand:

You can follow the state of the process for errors or important messagesby watching the output in the /var/log/mongodb/mongod.log file.

Begin using MongoDB.¶

Start a mongo shell on the same host machine as themongod. You can run the mongo shellwithout any command-line options to connect to amongod that is running on your localhost with defaultport 27017:

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

Brew Start Mongodb Free

To help you start using MongoDB, MongoDB provides GettingStarted Guides in various driver editions. For thedriver documentation, see Start Developing with MongoDB.

Uninstall MongoDB Community Edition¶

To completely remove MongoDB from a system, you must remove the MongoDBapplications themselves, the configuration files, and any directories containingdata and logs. The following section guides you through the necessary steps.

This process will completely remove MongoDB, its configuration, and alldatabases. This process is not reversible, so ensure that all of yourconfiguration and data is backed up before proceeding.

Stop MongoDB.¶

Stop the mongod process by issuing the following command:

Remove Packages.¶

Remove any MongoDB packages that you had previously installed.

Remove Data Directories.¶

Remove MongoDB databases and log files.

Additional Information¶

Localhost Binding by Default¶

Brew Start Mongodb 2020

By default, MongoDB launches with bindIp set to127.0.0.1, which binds to the localhost network interface. Thismeans that the mongod can only accept connections fromclients that are running on the same machine. Remote clients will not beable to connect to the mongod, and the mongod willnot be able to initialize a replica set unless this value is setto 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

Before binding to a non-localhost (e.g. publicly accessible)IP address, ensure you have secured your cluster from unauthorizedaccess. For a complete list of security recommendations, seeSecurity Checklist. At minimum, considerenabling authentication andhardening network infrastructure.

Brew Install Mongodb

For more information on configuring bindIp, seeIP Binding.

MongoDB Community Edition Packages¶

Brew Start Mongodb Error

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

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