Navigation
This version of the documentation is archived and no longer supported. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.

Start and Stop Ops Manager Application

On this page

Start the Ops Manager Server

Note

If you installed from a tar.gz or zip archive, you must create a symlink located at the path /etc/init.d/mongodb-mms that points to the <install_dir>/bin/mongodb-mms.

After configuring your Ops Manager deployment, you can start the Ops Manager Application with this command:

copy 
sudo /etc/init.d/mongodb-mms start

In some situations, starting MongoDB may take several minutes to pre-allocate the journal files. This is normal behavior.

To open Ops Manager, enter the URL specified in the URL to Access Ops Manager setting in the Ops Manager UI. If you are opening Ops Manager for the first time, enter the following URL, where <host> is the fully qualified domain name of the Ops Manager server. Ops Manager prompts you to register a new user when you login for the first time.

copy 
http://<host>:8080

Stop the Ops Manager Application

Enter the following command:

copy 
sudo /etc/init.d/mongodb-mms stop

Startup Log File Output

The Ops Manager Application logs its startup output to a logs directory of each Ops Manager host.

The log file for each Ops Manager instance is named mms#-startup.log, where # is a zero-based index of the Ops Manager instance. The log file for the Backup Daemon is named daemon-startup.log.

If the Ops Manager Application starts successfully, the init.d daemon creates log entries in this log file that resemble the following:

copy 
[main] INFO  ServerMain:202 - Starting mms...
[main] WARN  AbstractConnector:294 - Acceptors should be <=2*availableProcessors: SelectChannelConnector@0.0.0.0:0
[null] LoginService=HashLoginService identityService=org.eclipse.jetty.security.DefaultIdentityService@1eb3319f
[main] INFO  AppConfig:46 - Starting app for env: hosted
[main] INFO  MmsAppConfig:67 - Not loading backup components
[main] INFO  GraphiteSvcImpl:67 - Graphite service not configured, events will be ignored.
[main] INFO  TwilioSvcImpl:48 - Twilio service not configured, SMS events will be ignored.
[main] INFO  OpenDMKSnmpTrapAgentSvcImpl:91 - SNMP heartbeats hosts not configured, no heartbeat traps will be sent.
[main] INFO  ServerMain:266 - Started in: 24979 (ms)

Note

The startup log is rotated and retains the full history of all startup events. You can change its retention policy.

Optional: Run as Different User

  1. Edit <install_dir>/conf/mms.conf:

    copy 
    |mms|_USER=foo_user

  2. Change Ownership of <install_dir> for new user:

    sudo chown -R foo_user:foo_group <install_dir>

  3. Restart the Ops Manager Application:

    copy 
    sudo <install_dir>/bin/mongodb-mms restart

Optional: Ops Manager Application Server Port Number

  1. Edit <install_dir>/conf/conf-mms.properties:

    copy 
    mms.centralUrl=http://mms.example.com:<newport>

  2. Edit <install_dir>/conf/mms.conf

    copy 
    BASE_PORT=<newport>

  3. Restart the Ops Manager Application:

    copy 
    sudo <install_dir>/bin/mongodb-mms restart

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