- Administration >
- Start and Stop Ops Manager Application
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:
In some situations, starting MongoDB may take several minutes to pre-allocate the journal files. This is normal behavior.
You can now use Ops Manager 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, Ops Manager stores user accounts in the local MongoDB instance. When you sign into Ops Manager for the first time, the system will prompt you to register and create a new “group” for your deployment.
Stop the Ops Manager Application¶
Enter the following command:
Startup Log File Output¶
The Ops Manager Application logs its output to a logs
directory inside
the installation directory. You can view this log information with the
following command:
If the Ops Manager Application starts successfully, you will see content in this file that resembles the following:
Optional: Run as Different User¶
Edit
<install_dir>/conf/mms.conf
:Change Ownership of
<install_dir>
for new user:sudo chown -R foo_user:foo_group <install_dir>
Restart the Ops Manager Application:
Optional: Ops Manager Application Server Port Number¶
Edit
<install_dir>/conf/conf-mms.properties
:Edit
<install_dir>/conf/mms.conf
Restart the Ops Manager Application: