search cancel

Copying an updated custom probe package from the archive to robot agents is not updating

book

Article ID: 229924

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM) Unified Infrastructure Management for Mainframe

Issue/Introduction

Added a new file system to monitor in a custom CDM package. Sent the updated package to a list of agents and none of them are showing the added file system being monitored. 

Environment

Release : 20.3

Component : UIM - DISTSRV

Cause

- distsrv configuration/behaviour

Resolution

The probe configuration package can be deployed from the Primary to one of its child robots, and the package can be deployed from a remote hub with distsrv installed to one of its own child robots.

In the Primary hub distsrv setup a forwarding rule for the configuration package and confirm that the package forwarded from the distsrv on the Primary to the remote hub distsrv, then check to make sure it is in the remote hub's local archive.

Sometimes the distsrv task/job may appear to fail but it can be a temporary distsrv issue. The distsrv could be in a bad/hung state, so in that case, simply restart or cold start the distsrv and try again.

You can also try clearing out all of the distsrv jobs if the job still fails and throws an alarm saying that there is a problem with the package.

Deactivate the 'distsrv' probe
Rename the "jobs.history.db" file.  The default location is "C:\Program Files (x86)\Nimsoft\probes\service\distsrv"
Activate the 'distrsrv' probe
The "jobs.history.db" file will be rebuilt.
Test deployment again.