The wasp probe fails to start on a standalone Business Intelligence robot

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

The wasp probe fails to start on a standalone Business Intelligence (BI) robot

Key observations:

1. wasp probe with loglevel 1

wasp.log: Controller: Max. restarts reached for probe 'wasp' (command = <startup java21>)

2. wasp probe with loglevel 5

wasp.log: Controller: Max. restarts reached for probe 'wasp' (command = <startup java21>)

_wasp.log: [main, com.nimsoft.nimbus.lookup.DataEngineLookup] No crypt key

Cause

Any robot version with the wasp probe

Resolution

This issue is sometimes seen when the cryptkey parameter is not configured on the robot.

1. Copy the X:\Nimsoft\security\certificate.pem file from the Primary hub to the UIM BI robot.
2. Navigate to the <nimsoft>\robot folder
3. Open the robot.cfg file in a text editor.
4. Add the following parameter to the file:
   cryptkey = <location of the .pem file>
   For example, cryptkey = C:\Nimsoft\certificate\certificate.pem
5. Save the change.

6. Run "Security Validate" on the wasp probe.

Additional Information

Configure the robot.cfg File