automated_deployment_engine (ADE) probe will not start after deployment to secondary hub

Document ID : KB000044457
Last Modified Date : 14/02/2018
Show Technical Document Details

Symptoms:

After using Infrastructure Manager to deploy the automated_deployment_engine probe to a secondary hub, the probe fails to start.

After some time, the probe's icon turns red.

An error similar to the following will be deployed in the probe's log:

Dec 16 07:48:49:379 [0232] Controller: Max. restarts reached for probe 'automated_deployment_engine' (command = <startup java>)

Cause:

This is caused by an issue with the distsrv probe.

The distsrv probe is largely deprecated and its functionality has been replaced by the ADE probe itself.   Therefore, the issue cannot be fixed permanently in distsrv, but several workarounds are available.

The problem only occurs when the ADE probe has been forwarded to a remote distsrv and the remote distsrv attempts to install the package.  When the ADE probe is deployed from the primary archive, the problem does not occur.

Workarounds:

 

1. After deploying the ADE probe to a secondary hub, locate the following folder on the Primary hub:

\Nimsoft\probes\service\automated_deployment_egine\lib

Copy all the files from this folder and place them in the same location on the secondary, then restart the secondary robot.

 

2. Deactivate forwarding in all distsrv probes, then deploy the ADE probe so that the probe is deployed from the Primary archive.

 

3. Deploy the ADE probe from the Admin Console instead of Infrastructure Manager. The ADE probe on the primary hub will perform the actual probe deployment, not distsrv, and the problem will not occur.