This looks very similar to this issue.
Maybe you have a similar configuration error?
It is not clear from your problem description whether this is a network issue or an configuration issue.
So the first thing I would suggest is to check for full connectivity using pin/netcat.
Keep in mind that ROS requires full bi-directional connectivity between all pairs of machines, on all ports.
Moreover, make sure your ROS_MASTER_URI
, ROS_HOSTNAME
/ ROS_IP
are set correctly on all machines.
- In general
ROS_MASTER_URI
has to be set on each remote machine toROS_MASTER_URI=http://<hostname>:<used port>
or http://<master ip>:<used port>
- On the machine running the master you do not necessarily have to set
ROS_MASTER_URI
as it defaults to http://localhost:11311
, however, if using a custom port (as in your case) set it to http://localhost:<used port>
ROS_HOSTNAME
only has to be set manually on a machine if your systems default host names is not resolvable. - Alternatively to avoid taking care of the name resolution you can set
ROS_IP
to your external IP Address on each machine without a resolvable host name.
A basic tutorial on how to test and setup your network for ROS can be found here.
For a more specific answer please provide more details about your network configuration and your ROS environment.
Can you please give us some more information about what your setup is. Can you describe how you've setup your ROS environment, what lines you added to your
.bashrc
file, and what commands you ran to produce this error.Also, did you follow the suggestion to check if the machine can ping itself???