[ros-users] roslaunch for multiple machines

Ken Conley kwc at willowgarage.com
Wed Nov 17 18:08:16 UTC 2010


Hi Chris,

The problem appears to be with the machine you are running roslaunch
on. You need to set ROS_IP on it, as this is the default address it is
getting:

[http://***-toshibalaptop:43812/]

On an unrelated note, ros-package-path is misspelled in your machine tags.

HTH,
Ken

On Wed, Nov 17, 2010 at 9:47 AM, chris_li <gang.li at okstate.edu> wrote:
>
> This is my first time to use .launch file, I am trying to run some nodes on
> multiple machines.  I have gone through the tutorial and previous posts, but
> I still can not find where my mistake is.
>
> Here is my .launch file:
>
> <launch>
>
> <machine name="host" address="localhost" ros-root="/opt/ros/cturtle/ros"
> ros-packge-path="/opt/ros/cturtle/stacks" default="true" >
>    <env name="ROS_IP" value="192.168.1.100" />
> </machine>  %% set my localhost env variable
>
>
> <node name="GMapping_SLAM" pkg="gmapping" type="slam_gmapping"
> required="true" />
> %%node on my host machine
>
>
> <machine name="Fit" address="192.168.1.100" ros-root="/opt/ros/cturtle/ros"
> ros-packge-path="/opt/ros/cturtle/stacks" user="***" password="***"
> default="never" >
>    <env name="ROS_MASTER_URI" value="http://192.168.1.122:11311" />
>    <env name="ROS_IP" value="192.168.1.100" />
> </machine>  %%I am using my host machine's IP instead of its name
>
> <node name="Hokuyo" pkg="hokuyo_node" type="hokuyo_node" machine="Fit"
> required="true" />
> %%node on the other machine
>
> </launch>
>
>
> After I roslaunch this, I got this:
>
> ... logging to
> /home/***/.ros/log/7626bb9e-f10e-11df-bc03-00264daa5299/roslaunch-***-toshibalaptop-3036.log
> Checking log directory for disk usage. This may take awhile.
> Press Ctrl-C to interrupt
> Done checking log file disk usage. Usage is <1GB.
>
> started roslaunch server http://***-toshibalaptop:43812/
> remote[192.168.1.100-0] starting roslaunch
> remote[192.168.1.100-0]: creating ssh connection to 192.168.1.100:22,
> user[***]
> remote[192.168.1.100-0]: ssh connection created
> remote[192.168.1.100-0]: Exception while registering with roslaunch parent
> [http://***-toshibalaptop:43812/]: Traceback (most recent call last):
>  File "/opt/ros/cturtle/ros/tools/roslaunch/src/roslaunch/server.py", line
> 489, in _register_with_server
>    code, msg, _ = server.register(name, self.uri)
>  File "/usr/lib/python2.6/xmlrpclib.py", line 1199, in __call__
>    return self.__send(self.__name, args)
>  File "/usr/lib/python2.6/xmlrpclib.py", line 1489, in __request
>    verbose=self.__verbose
>  File "/usr/lib/python2.6/xmlrpclib.py", line 1235, in request
>    self.send_content(h, request_body)
>  File "/usr/lib/python2.6/xmlrpclib.py", line 1349, in send_content
>    connection.endheaders()
>  File "/usr/lib/python2.6/httplib.py", line 892, in endheaders
>    self._send_output()
>  File "/usr/lib/python2.6/httplib.py", line 764, in _send_output
>    self.send(msg)
>  File "/usr/lib/python2.6/httplib.py", line 723, in send
>    self.connect()
>  File "/usr/lib/python2.6/httplib.py", line 704, in connect
>    self.timeout)
>  File "/usr/lib/python2.6/socket.py", line 500, in create_connection
>    for res in getaddrinfo(host, port, 0, SOCK_STREAM):
> gaierror: [Errno -2] Name or service not known
>
>
> [192.168.1.100-0] killing on exit
> remote roslaunch failed to launch: Fit
>
>
> From the error message, it seems that the name or some path information is
> missing.  But I did set the env ROS_MASTER_URI and ROS_IP and, I also reset
> ros-root and ros-package-path for the remote machine. (this seems to be the
> problem in previous posts about roslaunch issues).
>
> Any suggestion is really appreciated~
>
> Chris
>
> --
> View this message in context: http://ros-users.122217.n3.nabble.com/roslaunch-for-multiple-machines-tp1918649p1918649.html
> Sent from the ROS-Users mailing list archive at Nabble.com.
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>



More information about the ros-users mailing list