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 Monitoring deployment, you can start the Ops Manager server 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.

You can now use the Monitoring instance by visiting the URL specified in the mms.centralUrl parameter (e.g. http://mms.example.com:8080) to continue configuration:

Unlike the SaaS version of Ops Manager, Monitoring stores user accounts in the local MongoDB instance. When you sign into the Monitoring instance for the first time, the system will prompt you to register and create a new “group” for your deployment.

Because there are no Monitoring Agents attached to your account, the first page you see in Monitoring will provide instructions for downloading the Monitoring Agent. Click the “download agent” link to download a pre-configured agent for your account. Continue reading this document for installation and configuration instructions for the Ops Manager agent.

Stop the Ops Manager Server

Enter the following command:

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

Startup Log File Output

The Ops Manager server logs its output to a logs directory inside the installation directory. You can view this log information with the following command:

copy 
sudo less <install_dir>/logs/mms0.log

If the server starts successfully, you will see content in this file that resembles 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 |mms| in: 24979 (ms)

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 Ops Manager server:

    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.acmewidgets.com:<newport>

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

    copy 
    BASE_PORT=<newport>

  3. Restart Ops Manager server:

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

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