cdm probe turns red and will not start nor write to the cdm.log.

book

Article ID: 182940

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

After upgrading the Primary hub to 9.0.2, the cdm probe will not start on the Primary. Other monitoring probes start and run without issue. View log results in ERROR: Not found and nothing is written to the log.

Cause

- The cdm probe had the cluster probe as a 'start_after' dependency but the cluster probe was deactivated.

Environment

Release : 9.0.2

Component : UIM - CDM WITH IOSTAT

Resolution

The cdm probe had the cluster probe as a 'start_after' dependency.

The cluster probe was disabled during the recent upgrade and tagged as 'not required.'

Customer started the cluster probe, then the cdm probe, and it started without any problem.

<cdm>
   description = CPU, Disk and Memory performance probe
   group = System
   active = error
   type = daemon
   command = cdm.exe
   config = cdm.cfg
   datafile = cdm.data
   logfile = cdm.log
   workdir = probes/system/cdm
   start_after = cluster
   magic_key = 5PkrTDps+SfpaDiJ8wE6xeG17rH0gFlJosCXzayfm7L/1kmLkssxxxxBSA+Bf6VI
</cdm>

Additional Information

Related controller.log entries

Controller: START: probe_activate

Controller: probe_activate (cdm) from 10.xx.xxx.xxx/57792
Controller: ciOpen - cache path: F:\Program Files (x86)\Nimsoft/niscache
Controller: send_alarm - name = 'cdm' level = '4' metric= 'Can not start cdm, start after probe not enabled ()' token = '10.2:4'msg = 'as#controller.probe_dependency.2'