Validate the installation
Follow the steps below to validate that the installation was successful.
Elasticsearch requires Java11. Java 11 is included with the installation of the RPM packages as a dependency.
If Elasticsearch fails to start due to an incorrect Java/JDK version, follow these steps.
-
Run the following command to configure the system to use the new Java version:
alternatives --config java
This command prompts you to select which 'java' should be in the system PATH. At the prompt, type the number which corresponds with the Java 11 installation. For example, if the prompt includes:
Selection Command ----------------------------------------------- *+ 1 java-8-openjdk.x86_64 (/usr/lib/jvm/java-8-openjdk-8.1.0.7-0.el7_6.x86_64/bin/java) + 2 java-11-openjdk.x86_64 (/usr/lib/jvm/java-11-openjdk-11.0.5.10-0.el7_7.x86_64/bin/java
Press 2 and hit Enter. To confirm the change has taken effect, run the following command:
java -version
The output should show the latest version of
openjdk
. This version will be at least11.0.5
. -
Restart Elasticsearch:
service elasticsearch restart
Perform the following steps to ensure that Moogsoft AIOps v7.3 has been successfully installed or upgraded:
-
Check that the UI login page displays "Version 8.x" at the bottom.
-
Log into the UI with username "admin" and password "admin". You should change the default username and password when you have logged in for the first time.
-
Select the Help icon (question mark) > Support Information. Check that the System Information shows "Version 8.x" and the correct schema upgrade history if you have performed an upgrade.
Note
If you have already completed this step previously (as part of this upgrade process) on the current host, you can skip this step.
Run the Install Validator utility to ensure that all Moogsoft AIOps
files were deployed correctly in $MOOGSOFT_HOME
:
$MOOGSOFT_HOME/bin/utils/moog_install_validator.sh
Run this utility to confirm that all Apache Tomcat files were deployed correctly in $MOOGSOFT_HOME
:
$MOOGSOFT_HOME/bin/utils/tomcat_install_validator.sh
If there are webapp differences, run the following command to extract the webapps with the correct files:
$MOOGSOFT_HOME/bin/utils/moog_init_ui.sh -w
Note
If you have already completed this step previously (as part of this upgrade process) on the current host, you can skip this step.
Run the Database Validator utility to validate the database schema:
$MOOGSOFT_HOME/bin/utils/moog_db_validator.sh
Note
Some schema differences are valid, for example those related to custom_info (new columns added etc).
An additional required schema upgrade step is documented on the Post-upgrade steps page. Until this has been run, you should expect to see the following differences in the output of the Database Validator utility:
Differences found in 'historic_moogdb' tables: 41,49c41,43 < primary key (`alert_id`), < unique key `idx_signature` (`signature`), < key `idx_first_event_time` (`first_event_time`), < key `idx_state_last` (`state`,`last_state_change`), < key `idx_severity` (`severity`,`state`), < key `idx_agent` (`agent`(12)), < key `idx_source` (`source`(12)), < key `idx_type` (`type`(12)), < key `idx_manager` (`manager`(12)) --- > primary key (`signature`), > key `alert_id` (`alert_id`), > key `first_event_time` (`first_event_time`,`alert_id`) 93,94c87 < key `timestamp` (`timestamp`,`type`), < key `idx_type_time` (`type`,`timestamp`) --- > key `timestamp` (`timestamp`,`type`) 241,242c234 < key `sig_id` (`sig_id`,`action_code`,`timestamp`), < key `idx_action_sig` (`action_code`,`sig_id`) --- > key `sig_id` (`sig_id`,`action_code`,`timestamp`)
The differences above will not have any functional impact, but you must complete the rest of the upgrade to ensure the system is performant and the schema is ready for future upgrades.
If you have performed an upgrade and you see errors similar to the following:
Differences found in 'moogdb' tables: 57a58 > key 'filter_id' ('filter_id'), 194a196 > key 'enrichment_static_mappings_ibfk_1' ('eid'), 1196a1199 > key 'sig_id' ('sig_id'), 1325a1329 > key 'filter_id' ('filter_id'),
Run the following commands to resolve these index-related problems:
mysql moogdb -u root -e "alter table alert_filters_access drop key filter_id" mysql moogdb -u root -e "alter table situation_filters_access drop key filter_id" mysql moogdb -u root -e "alter table enrichment_static_mappings drop key enrichment_static_mappings_ibfk_1" mysql moogdb -u root -e "alter table sig_stats_cache drop key sig_id"