| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Error message:
Unable to contact my own server at [http://192.168.0.2:38315/].
This usually means that the network is not configured properly.
A common cause is that the machine cannot ping itself. Please check
for errors by running:
ping 192.168.0.2
For more tips, please see
http://www.ros.org/wiki/ROS/NetworkSetup
The traceback for the exception was written to the log file
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.
ROS_MASTER_URI has to be set on each remote machine toROS_MASTER_URI=http://<hostname>:<used port> or http://<master ip>:<used port>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_HOSTNAMEonly has to be set manually on a machine if your systems default host names is not resolvable. 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.
Asked: 2019-09-10 09:29:02 -0500
Seen: 479 times
Last updated: Sep 12 '19
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
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
.bashrcfile, and what commands you ran to produce this error.Also, did you follow the suggestion to check if the machine can ping itself???