search cancel

UIM| Wasp probe is not starting on Primary hub

book

Article ID: 215991

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Wasp probe is not starting on the Primary hub, the _wasp.log shows the below errors:

May 26 14:49:25:261 ERROR [main, com.nimsoft.nimbus.probe.service.wasp.Probe] main() Fatal error!
May 26 14:49:25:266 ERROR [main, com.nimsoft.nimbus.probe.service.wasp.Probe] main() (90) Configuration error, No value found for key setup/data_engine
May 26 14:49:25:267 ERROR [main, com.nimsoft.nimbus.probe.service.wasp.Probe] (90) Configuration error, No value found for key setup/data_engine

Looking at the wasp.cfg and noticed it only contain reinitialize key and missing many of the required keys

<setup>
   reinitialize = true
</setup>

Environment

UIM 20.x

Wasp 20.3x

Cause

The main reason was the OC was installed on the primary hub which is not recommended.
A corruption happened to the wasp probe caused the wasp.cfg to lose its contains.


Resolution

1- On the primary hub run the OC-installer20.3.x and select Lunch the uninstaller for Operator Console 20.3.x


2- Run the OC-installer20.3.x and select a different robot to install the OC on.

3- Deploy Wasp probe to the Primary hub

4- Deploy adminconsoleapp, uimhome, and wasp_alarmviewer_api packages to the primary hub

to connect to the Admin Console 
browse to http://<UIM_IP_address>/adminconsoleapp/

to connect to the Operator Console 
browse to http://<OC_IP_address>/operatorconsole_portlet/

Attachments