Hub probe on the primary hub will not start - Probe hub FAILED to start, file check determines changes in the probe

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

hub probe on the primary hub is not getting started and we are not able to connect to primary hub. Below is message we are seeing in the hub logs.

 

Aug 29 02:54:45:663 [15048] Controller: Probe 'hub' FAILED to start, file check determines changes in the probe

Aug 29 02:59:17:212 [17784] Controller: Probe 'hub' FAILED to start, file check determines changes in the probe

Aug 29 03:01:55:348 [5976] Controller: Probe 'hub' FAILED to start, file check determines changes in the probe

Environment

Release : 9.x

Component : UNIFIED INFRASTRUCTURE MGMT

Resolution

Need to reset the magic_key to allow the probe to start

1. edit controller.cfg on primary hub
2. locate the <Hub> section
3. delete the entire magic_key line from the <hub> section
4. move controller.cfg to the nimsoft/robot/changes folder
5. restart the nimsoft robot watcher service on primary hub

Controller will process the changes folder create a new magic key for the hub probe and move the controller.cfg back to robot folder. After this the hub probe will start