Moogsoft Docs

Upgrade Non-root v7.0.0 to Non-root v7.0.1

This topic describes the upgrade procedure of non-root deployments from Moogsoft AIOps v7.0.0 non-root to Moogsoft AIOps v7.0.1 non-root.

The following steps outline this workflow:

Before You Begin

Red Hat Enterprise Linux 6/CentOS 6 (RHEL6) is not supported for Moogsoft AIOps v7.0.1. See Deprecation Notice: RHEL 6

To do this workflow, you must be logged in as the same non-root user that installed and runs the existing Moogsoft AIOps v6.5.0 software.

Download the New Installer

Run the following command to download the installer:

curl -L -O "https://<username>:<password>"

Back Up the Existing System

To back up the existing system:

  1. Back up $MOOGSOFT_HOME .
  2. Take a snapshot (for VMs).
  3. Back up MySQL.

Stop Processes

  1. Stop moog_farmd :

    $MOOGSOFT_HOME/bin/utils/process_cntl moog_farmd stop
  2. Stop Apache Tomcat:

    $MOOGSOFT_HOME/bin/utils/process_cntl apache-tomcat stop
  3. Stop the LAMs. You can use either process_cntl or kill .
    Using process_cntl :

    $MOOGSOFT_HOME/bin/utils/process_cntl <lam_name> stop

    Using kill :

    kill -9 $(ps -ef | grep java | grep lam | awk '{print $2}') 2>/dev/null
  4. Disable the events_analyser from running during the upgrade process:
    1. Run the following command to comment out the relevant lines in crontab :

      (crontab -l | sed -e 's/^\(.*events_analyser.*\)$/#\1/') | crontab -
    2. Run the following command to stop any running events_analyser processes:

      ps -ef | grep java | egrep 'events_analyser|moog_indexer' | awk '{print $2}' | xargs kill 2>/dev/null
  5. Stop mysql , rabbitmq , elasticsearch , nginx , and tomcat :

    $MOOGSOFT_HOME/bin/utils/process_cntl mysqld stop
    $MOOGSOFT_HOME/bin/utils/process_cntl elasticsearch stop
    $MOOGSOFT_HOME/bin/utils/process_cntl rabbitmq stop
    $MOOGSOFT_HOME/bin/utils/process_cntl nginx stop

Upgrade Moogsoft AIOps

Run the following commands to perform the upgrade:

tar -xf moogsoft-aiops-7.0.1.tgz

Follow the instructions. It detects the v7.0.0 installation and performs an upgrade (a side-by-side deployment).

Merge the Latest Config File Changes

The top-level $MOOGSOFT_HOME/config and $MOOGSOFT_HOME/bots folders are the master folder locations for config and bot files. The new 'default' v7.0.1 versions of these files are stored under $MOOGSOFT_HOME/dist/7.0.1/config/ and $MOOGSOFT_HOME/dist/7.0.1/bots/ respectively.

  1. Identify the 'config' files that have changed between v6.5.0 and v7.0.1. For example:

    diff -rq $MOOGSOFT_HOME/dist/7.0.0*/config $MOOGSOFT_HOME/dist/7.0.1/config | grep -i 'differ'
  2. Update the files in $MOOGSOFT_HOME/config/ with any changes introduced in the v7.0.1 versions of these files.

Upgrade Apache Tomcat and Nginx

Enter the following commands to upgrade Apache Tomcat and Nginx:

$MOOGSOFT_HOME/bin/utils/ -qtnfwz $($MOOGSOFT_HOME/bin/utils/moog_config_reader -k --accept-eula

Migrate the certificates for the previous deployment of Nginx to the new deployment. Use the following commands as an example of how to do this in the general case where SSL terminates in Nginx (default configuration):

CERT_PATH_PEM=$(grep 'ssl_certificate ' $MOOGSOFT_HOME/dist/7.0.0*/cots/nginx/config/conf.d/moog-ssl.conf)
CERT_PATH_KEY=$(grep 'ssl_certificate_key' $MOOGSOFT_HOME/dist/7.0.0*/cots/nginx/config/conf.d/moog-ssl.conf)
cp -f $(echo "${CERT_PATH_PEM:0:-1}" | awk '{print $2}') $MOOGSOFT_HOME/dist/7.0.1/cots/nginx/ssl/
cp -f $(echo "${CERT_PATH_KEY:0:-1}" | awk '{print $2}') $MOOGSOFT_HOME/dist/7.0.1/cots/nginx/ssl/
sed -i "s|.*ssl_certificate .*|${CERT_PATH_PEM}|" $MOOGSOFT_HOME/dist/7.0.1/cots/nginx/config/conf.d/moog-ssl.conf
sed -i "s|.*ssl_certificate_key.*|${CERT_PATH_KEY}|" $MOOGSOFT_HOME/dist/7.0.1/cots/nginx/config/conf.d/moog-ssl.conf

Restart Nginx

$MOOGSOFT_HOME/bin/utils/process_cntl nginx restart

Update the Integrations

To update the integrations:

  1. Run the following command to extract the Integrations:

    bash $MOOGSOFT_HOME/bin/utils/integration_installer -a -l WARN;
    for file in $(diff -qr $MOOGSOFT_HOME/dist/7.0.1/ui/integrations/ \
    $MOOGSOFT_HOME/dist/7.0.0*/ui/integrations/ | egrep -vi 'only in.*7.0.1|differ' \
    | awk '{print $NF}'); do cp -rp "$MOOGSOFT_HOME/dist/7.0.0*/ui/integrations/$file" \
    $MOOGSOFT_HOME/dist/7.0.1/ui/integrations/; done

Confirm All Processes are Running and Start moogfarmd

To confirm all services are running:

  1. Run the following commands to verify that all required processes are running and to start moogfarmd:

    $MOOGSOFT_HOME/bin/utils/process_cntl apache-tomcat status
    $MOOGSOFT_HOME/bin/utils/process_cntl moog_farmd start
    $MOOGSOFT_HOME/bin/utils/process_cntl nginx status
    $MOOGSOFT_HOME/bin/utils/process_cntl elasticsearch status
  2. Run the following command to re-enable the events_analyser cronjobs:

    (crontab -l | sed -e 's/^\#\+\(.*events_analyser.*\)/\1/') | crontab -
  3. Run the following command to restart any previously running UI-based Integrations:

    bash $MOOGSOFT_HOME/bin/utils/startup_cntl;

Migrate the Java Keystore

The upgrade includes a new version of the Java Runtime, so you need to migrate any certificates stored in the old Java keystore into the new keystore, which is now the JRE under $MOOGSOFT_HOME/cots/jre/ .

The previous JRE is under $MOOGSOFT_HOME/dist/7.0.0/cots/jre .

If you did not manually add certificates to the old store, you can skip this step.

Verify the Upgrade

You can verify the upgrade manually or using automatic utilities.

Verify the Upgrade Manually

Perform the following basic steps to ensure the upgrade to Moogsoft AIOps v7.0.1 was successful:

  1. Verify that the UI login page displays "Version 7.0.1" at the top.
  2. Check that the UI "Support Information" window correctly indicates the current version as  "7.0.1" and shows the correct schema upgrade history.

Verify the Upgrade Using Automatic Utilities

Run the following automatic utilities to ensure that the upgrade to 7.0.1 was successful:

  1. Verify that Moog files are deployed correctly within $MOOGSOFT_HOME using this utility:

  2. Verify that all Apache Tomcat files are deployed correctly within $MOOGSOFT_HOME using this utility:

  3. Verify that all the steps are successful. If there are some webapp differences, run the following command to extract the webapp with the correct files:

    $MOOGSOFT_HOME/bin/utils/ -w
  4. Verify that the schema has upgraded successfully:

  • Confirm that all the steps are successful. Some schema differences might be valid (e.g. custom_info related). If there are more substantial differences, you should investigate further to verify that all the pre-requisite upgrade scripts have been applied in the right order:

    mysql -u root <moogdb_database_name> -e "select * from schema_upgrades;"
    mysql -u root <moog_reference_database_name> -e "select * from schema_upgrades;"


If you have any issues, refer to Troubleshooting .