wasp fails to start with 'get_connection_string' name = 'null' after an HA failback
search cancel

wasp fails to start with 'get_connection_string' name = 'null' after an HA failback

book

Article ID: 189533

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Environment
UIM 9.20 with an HA hub configured with two UMP

Problem:
wasp probe fails to start and captures the error below on both UMPs after an HA failback

Cannot obtain connection string from data_engine
(4) not found, Received status (4) on response (for sendRcv) for cmd = 'get_connection_string' name = 'null'

Environment

Release : 9.0.2

Component : UIM - UMP

Resolution

1. Edit the wasp.cfg on each UMP and remove the connection = %string%
Leave connection parameter blank:
Example: connection =

2. Confirm if the cryptkey parameter has the correct certificate.pem file path on both UMPs robot.cfg

3. Copy the certificate.pem file from the UIM server to both UMPs to rule out *.pem file corruption

4. Review the wasp ump_common and setup section and confirm if the addresses point to the Primary server

5. Correct the ump_common and setup section if the Primary probe address are incorrect.

6. Deactivated/Activated the wasp probe on the primary UMP followed by the secondary