This technical document provides a solution for an issue where the nic_monitor probe fails to start.
Symptoms of this issue:
1. Robot controller logs may display the below error:
Controller: _ProcStart - Probe 'nic_monitor' - starting
Controller: Max. restarts reached for probe 'nic_monitor' (command = <startup java>)
Controller: send_internal_alarm - failed to flush message (communication error)
Controller: Going down...
Controller: Down
2. nic_monitor probe logs may display the below error:
Controller: Max. restarts reached for probe 'nic_monitor' (command = <startup java>)
nic_monitor probe
This problem occurs when the robot (where the probe instance runs) has strict_ip_binding enabled.
Probe start-up arguments are like as follows:
Windows: arguments = -DNIMV_CONTIP=$NIMV_CONTIP -DNIMCPRID=$NIMCPRID -DNIM_PROBE_KEY=$NIM_PROBE_KEY -DNIMPROBEPORT=$NIMPROBEPORT -Djava.library.path=./lib -cp "lib/*" com.ca.uim.probes.nic_monitor.Probe
Linux: arguments = -DNIMV_CONTIP=$NIMV_CONTIP -DNIMCPRID=$NIMCPRID -DNIM_PROBE_KEY=$NIM_PROBE_KEY -DNIMPROBEPORT=$NIMPROBEPORT -Djava.library.path=../../../lib -cp lib/* com.ca.uim.probes.nic_monitor.Probe
Note: NIMV_CONTIP should be replaced by NIMBUS_LOCAL_IP.
1. Shut down the nimsoft robot watcher service on the robot in question.
2. Open the robot controller.cfg.
3. Remove -DNIMV_CONTIP=$NIMV_CONTIP" or replace by -DNIMV_CONTIP=$NIMBUS_LOCAL_IP".
4. Restart the robot.
The issue should now be resolved.