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.

Update On-Prem MongoDB Management Service

Update the Monitoring Agent

Update the Agent on UNIX/Linux

To update the Monitoring agent on UNIX/Linux systems:

  1. Stop the agent processes.
  2. Download the latest Monitoring agent from the Settings page of the MMS console, in the Monitoring Agent section.
  3. Restart the Monitoring agent.

Update the Agent on Windows

To update the agent on Windows systems:

  1. Download the latest Monitoring agent from the “Settings” page of the MMS console in the Monitoring Agent section).

  2. From a command shell, issue the following:

    sc stop MongoMMS
    sc delete MongoMMS
    

    This should stop and uninstall On Prem MMS Monitoring.

  3. Confirm that the service no longer exists. Issue the following command:

    sc query MongoMMS
    

    This operation will return a message that resembles the following:

    [SC] EnumQueryServicesStatus:OpenService FAILED 1060:
    
    The specified service does not exist as an installed service.
    
  4. When you have successfully uninstalled the Monitoring agent, you can use mongommsinstall.bat to reinstall On Prem MMS Monitoring.

  5. Restart the agent.

Upgrade MMS Packages

Upgrading an RPM-Based Installation

Please contact MMS to receive the download location of the latest MMS server release.

  1. Shutdown the On-Prem MMS server and take a backup of your existing configuration:

    sudo /etc/init.d/mongodb-mms stop
    sudo cp -a <install_dir>/conf ~/mms_conf.backup
    
  2. Perform an RPM upgrade:

    sudo rpm -Uvh 10gen-mms-<version>.x86_64.rpm
    
  3. Reconcile any changes in configuration files.

    At this point the upgrade is complete. However you may need to reconcile changes in your configuration with new configuration options available in the latest release.

    During the rpm operation, if you saw the following output, you have changes to reconcile:

    warning: <install_dir>/conf/conf-mms.properties created as    <install_dir>/conf/conf-mms.properties.rpmnew
    

    Compare your current configuration to the updated version, with the following sequence of operations:

    diff -u <install_dir>/conf/conf-mms.properties <install_dir>/conf/conf-mms.properties.rpmnew
    diff -u <install_dir>/conf/mms.conf <install_dir>/conf/mms.conf.rpmnew
    

    Edit your configuration to resolve any conflicts between the old and new versions, being sure to take any new changes from conf-mms.properties.rpmnew as appropriate. Changes to mms.centralUri, email addresses, and MongoDB are the most common configuration changes.

    Repeat the above reconciliation for mms.conf if the upgrade indicates a conflict.

    Note

    The upgrade from beta versions 1.0.1 to 1.0.2 changed several paths to make the MMS server completely self contained. In 1.0.2 all logs, configuration, and working files are in the /opt/10gen/mms/ hierarchy. This changes the following paths from 1.0.1:

    • New logs path: <install_dir>/logs/
    • New tmp path: <install_dir>/tmp/

    Finally, you may also need to re-symlink your startup script:

    sudo ln -s /<install_dir>/bin/mongodb-mms /etc/init.d/mongodb-mms
    
  4. Restart the On-Prem MMS server.

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

Upgrading a tgz/zip Installation

To upgrade a tarball installation, backup configuration and/or logs, and then re-install the On-Prem MMS server.

Important

It is crucial that you back up the existing configuration because the upgrade process will delete existing data.

In more details:

  1. Shutdown the MMS server and take a backup of your existing configuration and logs.

    sudo /etc/init.d/mongodb-mms stop
    sudo cp -a <install_dir>/conf ~/mms_conf.backup
    sudo cp -a <install_dir>/logs ~/mms_logs.backup
    
  2. Remove your existing MMS server installation entirely and extract latest release in its place:

    cd <install_dir>/../
    sudo rm -rf <install_dir>
    sudo tar -zxf -C . /path/to/10gen-mms-<version>.x86_64.tar.gz
    
  3. Similar to the RPM upgrade path above, compare and reconcile any changes in configuration between versions:

    diff -u ~/mms_conf.backup/conf-mms.properties <install_dir>/conf/conf-mms.properties
    diff -u ~/mms_conf.backup/mms.conf <install_dir>/conf/mms.conf
    
  4. Edit your configuration to resolve any conflicts between the old and new versions, being sure to take any new changes as appropriate.

    Note

    Changes to mms.centralUri, email addresses, and MongoDB are the most common configuration changes.

  5. Restart the On-Prem MMS server.

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