RPM - Upgrade data ingestion components

Run the following commands as root to query/stop the default LAM/integrations services on any servers with the moogsoft-integrations/moogsoft-integrations-ui package installed and where the LAMs/integrations are running.

Check for running LAM and integration processes and stop them using the relevant service scripts:

systemctl status | grep lamd
 
service <lam_service_name> stop

Run the following command to stop any remaining active LAM and integration processes:

kill -9 $(ps -ef | grep java | grep CLamMain | awk '{print $2}') 2>/dev/null

To upgrade Moogsoft Enterprise, run the upgrade command below that corresponds to your chosen upgrade mechanism.

If you have already run this step on the current host as part of this upgrade (for single-host upgrade for example), you can skip this step.

Manually merge and compare .rpmsave versions of files with the new versions of those files. Add any new properties to the older versions of the files. You can skip this step if you have already completed this step as part of this upgrade process on the current host.

The config and bot files from the previous version should not be copied on top of (replace) the new version of those files in 7.3.x, as they are not always forwards-compatible, and some config/bot lines need to be added for the new version to work.

To find files that have been changed, moved or deleted, run these commands:

find $MOOGSOFT_HOME -name '*.rpmsave'
find /etc/init.d/ -name '*.rpmsave'

For example, the following command displays the differences in the new version of the system.conf file:

diff -u $MOOGSOFT_HOME/config/system.conf $MOOGSOFT_HOME/config/system.conf.rpmsave

Follow this process to merge the file differences:

Install the latest Java packages using the command below. It's possible that the yum upgrade of the moogsoft packages will have done this already and even possibly installed a newer version of Java than the one below. In this case, yum will report the packages are already installed and are the latest version. Continue with the subsequent steps even if this is the case.

VERSION=11.0.14.1.1; yum install java-11-openjdk-${VERSION} java-11-openjdk-devel-${VERSION} java-11-openjdk-headless-${VERSION};

On each server with a Moogsoft Enterprise RPM package installed, run the following command to replace the /usr/java/latest symlink so it points at the JDK11 JAVA_HOME directory:

source $MOOGSOFT_HOME/bin/utils/moog_init_functions.sh

If there are non-Moogsoft Enterprise packages on this server that do not support JDK11, you must update those applications to use a different JAVA_HOME symlink (not /usr/java/latest).

You can skip this step if you have already completed this step as part of this upgrade process on the current host.

To confirm this has worked, run the following command:

$JAVA_HOME/bin/java -version

It should return (as a minimum version):

openjdk version "11.0.14.1.1"

You can also use the 'alternatives' command to point the system 'java' shortcut to the new version:

alternatives --config java

The MySQL connector is upgraded in this release.

The original connector may be used by the External Database module in the current deployment, configured in $MOOGSOFT_HOME/config/moog_external_db_details.conf.

If this file is configured in the current deployment, update it to reference the new mariadb connector here: $MOOGSOFT_HOME/lib/cots/mariadb-java-client-2.4.0.jar.

You can skip this step if you have already completed this step as part of this upgrade process on the current host.

If you have RabbitMQ installed and running on this server, complete the following step.

Moogsoft recommends that you update the RabbitMQ configuration to support autoheal and other processes that improve stability in HA environments.

Run the command(s) below which are appropriate for the deployment type.