Linux robot communication error - Unable to reach controller, error message communication error
Article ID: 34342
Updated On:
Products
NIMSOFT PROBES
DX Infrastructure Management
Issue/Introduction
Some Linux environments have trouble auto-detecting the local IP which causes problems with probes listening for incoming connections.
Environment
Release:
Component: CAUIM
Component: CAUIM
Resolution
The first thing to try is to manually set the specific hostname and IP address in the robot.cfg file under /opt/nimsoft directory.
Leave all defaults in place except the following three lines:
...
Also, it is important to note that the local firewall may play a role here; generally speaking you should open ports 48000-48100 on any Nimsoft Robot, allowing connections from all other machines on the local network.
Leave all defaults in place except the following three lines:
...
robotname = set this to the computer hostname (shortname)
robotip = set this to the local/internal IP address of the machine
first_probe_port = 48000
robotip = set this to the local/internal IP address of the machine
first_probe_port = 48000
Also, it is important to note that the local firewall may play a role here; generally speaking you should open ports 48000-48100 on any Nimsoft Robot, allowing connections from all other machines on the local network.
Feedback
Powered by
