Skip to main content

Patch Moogsoft Onprem Tarball for v9.0.0.x

This topic describes how to patch a tarball-based distribution of Moogsoft Onprem to v9.0.0.2 from v9.0.0 or v9.0.0.x


  • The RabbitMQ upgrade as part of this process requires feature flags to be enabled.

  • The following command must be run on all RabbitMQ server nodes before the following steps are performed:

    export PATH=$MOOGSOFT_HOME/cots/erlang/bin/:$PATH;
    ${MOOGSOFT_HOME}/cots/rabbitmq-server/sbin/rabbitmqctl enable_feature_flag all
  1. Ensure the patch tarball is available to each server being patched:

    • Download the patch tarball using the following command (SPEEDY_USERNAME and SPEEDY_PASSWORD need to be set as environment variables before running this):

      curl -L -O "https://${SPEEDY_USERNAME}:${SPEEDY_PASSWORD}"

      Copy the tarball to all servers where the product is installed.

  2. Optional GPG key validation of the tarball to validate the installation file.

    • For servers without internet access (if server has internet access go to the next step):

      1. Download the key from this site: 
      2. Copy the key to the server onto which the tarball will be installed (it will be an .asc file).

      3. Import the key:

        gpg --import 0A8FD9AB6F1693A1967B3B8CB919E617EC6946C2 
    • For servers with internet access, run the following command:

      curl | gpg —-import
      1. Download the patch tarball and matching '.sig' file from the 'speedy' yum repository using a browser, providing speedy credentials when asked by the browser:
    • Copy the patch tgz and matching '.sig' file into the same folder.

    • Copy the following code into a bash terminal and run it to perform the validation:

      gpg --verify moogsoft-enterprise- moogsoft-enterprise-
    • Confirm that the command reports:

      Good signature from "Moogsoft <>"
  3. Stop all processes on each host:

    $MOOGSOFT_HOME/bin/utils/process_cntl moog_farmd stop;
    $MOOGSOFT_HOME/bin/utils/process_cntl apache-tomcat stop;
    kill -9 $(ps -ef | grep java | grep lam | awk '{print $2}') 2>/dev/null;
    (crontab -l | sed -e 's/^\(.*events_analyser.*\)$/#\1/') | crontab -
    (crontab -l | sed -e 's/^\(.*keepalive.*\)$/#\1/') | crontab -
    ps -ef | grep java | egrep 'events_analyser|keepalive' | awk '{print $2}' | xargs kill 2>/dev/null;
    $MOOGSOFT_HOME/bin/utils/process_cntl nginx stop;
  4. Gather the required variables (do not close the terminal these commands are run in, otherwise they will be lost):

    export OLD_DIST_PATH=$(readlink -f $MOOGSOFT_HOME/bin|awk -F '/' 'sub(FS $NF,x)');
    export CERT_REAL_PATH_PEM=$(readlink -f $(grep -h 'ssl_certificate ' $OLD_DIST_PATH/cots/nginx/config/conf.d/moog-ssl.conf|awk '{print $2}'|tr -d ';'));
    export CERT_REAL_PATH_KEY=$(readlink -f $(grep -h 'ssl_certificate_key' $OLD_DIST_PATH/cots/nginx/config/conf.d/moog-ssl.conf|awk '{print $2}'|tr -d ';'));
    export CERT_PATH_PEM=$(grep -h 'ssl_certificate ' $OLD_DIST_PATH/cots/nginx/config/conf.d/moog-ssl.conf);
    export CERT_PATH_KEY=$(grep -h 'ssl_certificate_key' $OLD_DIST_PATH/cots/nginx/config/conf.d/moog-ssl.conf);


  6. Place the downloaded tarball file into an empty directory called patch_directory9.0.0.2 and execute the following commands to start the patch installation:

    cd patch_directory9.0.0.2;
    tar -xf moogsoft-enterprise-;

    Now the RabbitMQ binaries have been upgraded, the RabbitMQ nodes need to be restarted.

    export PATH=$MOOGSOFT_HOME/cots/erlang/bin/:$PATH;
    $MOOGSOFT_HOME/bin/utils/process_cntl rabbitmq restart

    Perform some health checks (for example as documented here: to ensure the cluster is operating as expected

  8. There are changes in controller.conf, system.conf, and security.conf in this release (depending on the version being upgraded from). Identify the config files that have changed between the previously installed version and this version. For example:

    diff -rq $OLD_DIST_PATH/config $MOOGSOFT_HOME/dist/ | grep -i 'differ'

    Update files in $MOOGSOFT_HOME/config with any changes introduced in the 9.1.0 version of these files (if appropriate/needed).


    Refresh all stored procedures (provide the 'ermintrude' DB user password when prompted):

    $MOOGSOFT_HOME/bin/utils/moog_db_auto_upgrader -t 9.0.0 -u ermintrude

    Re-deploy Apache Tomcat and reconfigure Nginx. IMPORTANT: If the Xmx value for apache-tomcat has been changed from the default in the $MOOGSOFT_HOME/bin/utils/process_cntl script, ensure the customised value is replaced after the upgrade, then restart the apache-tomcat process. Run these commands in the same terminal as the one where the variables were saved previously. Then restart nginx:

    $MOOGSOFT_HOME/bin/utils/ -tnfwz $($MOOGSOFT_HOME/bin/utils/moog_config_reader -k --accept-eula
    cp -f $CERT_REAL_PATH_PEM $MOOGSOFT_HOME/cots/nginx/ssl/;
    cp -f $CERT_REAL_PATH_KEY $MOOGSOFT_HOME/cots/nginx/ssl/;
    sed -i "s|.*ssl_certificate .*|${CERT_PATH_PEM}|" $MOOGSOFT_HOME/cots/nginx/config/conf.d/moog-ssl.conf;
    sed -i "s|.*ssl_certificate_key.*|${CERT_PATH_KEY}|" $MOOGSOFT_HOME/cots/nginx/config/conf.d/moog-ssl.conf;
    $MOOGSOFT_HOME/bin/utils/process_cntl nginx restart;
  11. Verify the remaining processes are working properly and update the crontab:

    $MOOGSOFT_HOME/bin/utils/process_cntl apache-tomcat status;
    $MOOGSOFT_HOME/bin/utils/process_cntl nginx status;
    $MOOGSOFT_HOME/bin/utils/process_cntl opensearch status;
    (crontab -l | sed -e 's/^\#\+\(.*events_analyser.*\)/\1/') | crontab -
    (crontab -l | sed -e 's/^\#\+\(.*keepalive.*\)/\1/') | crontab -
  12. Validate the patch:


    If there are any errors from the above validators, please contact Moogsoft Support.

  13. Re-start non-UI integrations or LAMs

  14. Re-install the latest Add-ons pack: Install Moogsoft Add-ons

  15. Restart moogfarmd:

    $MOOGSOFT_HOME/bin/utils/process_cntl moog_farmd restart;
  16. Restart any event feeds if they were stopped.

  17. Clear the browser cache and log in to the UI.