Wasp probe fails to start when upgrading to Operator Console 23.4CU5

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

When upgrading to OC 23.4.5, the upgrade is able to successfully complete, but times out when waiting for the wasp probe to start.  The wasp probe appears to have frozen and stopped updating the logs.

Environment

• DX UIM 23.4CU5
• Operator Console 23.4CU5

Cause

The webapps, which should only be on the primary hub, were found to be deployed in OC:

uimhome
adminconsoleapp
uimesdplatelemetry
mps

These webapps are not normally deployed to the OC and are not updated with the upgrade.  As the Operator Console uses the new Java 21 released with UIM 23.4CU5 and the old webapps expect Java 8, they fail.  This causes the wasp probe to not progress through the normal startup process.

Resolution

The following steps prevented the wrong webapps from being started and allowed the wasp probe to continue.

 

1. Edit the wasp probe config file, or using the AC or IM configuration GUI.
   
   
2. For each of the 4 webapps, set the load_on_startup key=false (or manual in the GUI):
   uimhome
   adminconsoleapp
   uimesdplatelemetry
   mps
   
   
   
   
3. Deactivate/Activate the wasp probe.