Monitoring probe does not start

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

A monitoring probe will not start.  The probes logs are not updated.  The probe immediately turns red.

In the controller logs, the following is observed.

 Jan 16 14:09:29:105 [8184] 4 Controller: send_alarm - name = 'logmon' level = '4' metric = 'Can not start logmon, start after probe not enabled ()' token = '10.2:4' msg = 'as#controller.probe_dependency.2'

Environment

UIM 20.4+

Cause

Some probes may have dependencies.  They require that another probe be started before it will be allowed to start.  If that probe is not started, this alarm will occur.

Resolution

Check the controller.cfg file for the section for the probe that will not start.  Look for the start_after key:

<logmon>
...
    start_after = hdb
...
</logmon>

In this case, the hdb probe is dependent.  Check the controller.cfg file for this probe and check the active key:

<hdb>
...
    active = no
...
</hdb>

When the active key is set to 'no' it will not start.  Activating the dependent probe in AC or IM will allow the probes to restart properly. 
You can also edit the controller.cfg file and set this active key to 'yes'.  Restarting the robot with this key set to yes will allow the probes to start as needed.