ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Problem with remote nodes after ros packages upgrade

asked 2011-06-07 21:47:57 -0500

chcorbato gravatar image

updated 2011-06-09 09:49:55 -0500


Last June 6 I performed the available upgrade of ros packages, and now I'm experiencing an strange problem: using the same roslaunch files I had now the nodes in remote machines (for me those responsible for robot I/O) doesn't start up. They bring up when using a local launch file, so maybe this is an issue with roslaunch?

Now I've checked that they actually start up, but then die inmediately after.

I changed nothing in my launch files, so I was wondering wether this was an issue of the upgrade in the ros_comm stack

Thank you in advance for your comments


I'm using diamondback in Ubuntu 10.04, and here I list the ros packages I updated through Synaptic:

Commit Log for Mon Jun  6 10:11:25 2011
Upgraded the following packages:
ros-diamondback-camera-drivers (1.4.1-s1299038009~lucid) to 1.4.1-s1306620563~lucid
ros-diamondback-common (1.4.3-s1299027615~lucid) to 1.4.3-s1306609639~lucid
ros-diamondback-common-msgs (1.4.0-s1299027519~lucid) to 1.4.0-s1306609559~lucid
ros-diamondback-common-tutorials (0.1.2-s1299053657~lucid) to 0.1.2-s1306638686~lucid
ros-diamondback-control (0.1.1-s1299033115~lucid) to 0.1.1-s1306616386~lucid
ros-diamondback-desktop-full (1.0.0-s1304391878~lucid) to 1.0.0-s1306677492~lucid
ros-diamondback-diagnostics (1.4.0-s1299028141~lucid) to 1.4.0-s1306609964~lucid
ros-diamondback-diagnostics-monitors (1.4.0-s1299038404~lucid) to 1.4.0-s1306621047~lucid
ros-diamondback-documentation (1.4.1-s1299054311~lucid) to 1.4.1-s1306639612~lucid
ros-diamondback-driver-common (1.2.3-s1299028246~lucid) to 1.2.3-s1306610051~lucid
ros-diamondback-erratic-robot (0.2.0-s1304359692~lucid) to 0.2.0-s1306635164~lucid
ros-diamondback-executive-smach (1.0.1-s1299034118~lucid) to 1.0.1-s1306617318~lucid
ros-diamondback-executive-smach-visualization (1.0.1-s1299051085~lucid) to 1.0.1-s1306636595~lucid
ros-diamondback-geometry (1.4.1-s1299027775~lucid) to 1.4.2-s1306609794~lucid
ros-diamondback-geometry-experimental (0.1.4-s1299035647~lucid) to 0.1.5-s1306618067~lucid
ros-diamondback-geometry-tutorials (0.1.3-s1299042659~lucid) to 0.1.3-s1306625345~lucid
ros-diamondback-image-common (1.4.1-s1299029638~lucid) to 1.4.1-s1306610124~lucid
ros-diamondback-image-pipeline (1.4.1-s1302036824~lucid) to 1.4.2-s1306619150~lucid
ros-diamondback-image-transport-plugins (1.4.1-s1302032693~lucid) to 1.4.1-s1306610938~lucid
ros-diamondback-joystick-drivers (1.4.1-s1301689512~lucid) to 1.4.1-s1306611037~lucid
ros-diamondback-kinect (0.1.6-s1302037168~lucid) to 0.1.6-s1306620703~lucid
ros-diamondback-kinematics (0.3.3-s1304034970~lucid) to 0.3.3-s1306615328~lucid
ros-diamondback-laser-drivers (1.2.2-s1299041777~lucid) to 1.2.2-s1306624585~lucid
ros-diamondback-laser-pipeline (1.2.0-s1299027967~lucid) to 1.2.0-s1306612505~lucid
ros-diamondback-motion-planners (0.3.9-s1304352571~lucid) to 0.3.9-s1306615697~lucid
ros-diamondback-motion-planning-common (0.3.6-s1304034571~lucid) to 0.3.6-s1306615012~lucid
ros-diamondback-motion-planning-environment (0.3.1-s1298601768~lucid) to 0.3.1-s1306619083~lucid
ros-diamondback-motion-planning-visualization (0.3.1-s1298607902~lucid) to 0.3.1-s1306625171~lucid
ros-diamondback-navigation (1.4.1-s1301523272~lucid) to 1.4.1-s1306612684~lucid
ros-diamondback-openni-kinect (0.1.3-s1302657579~lucid) to 0.2.1-s1306611764~lucid
ros-diamondback-orocos-toolchain-ros (0.3.2-s1304497659~lucid) to 0.3.2-s1306628274~lucid
ros-diamondback-perception-pcl (0.10.0-s1299028346~lucid) to 0.10.0-s1306611175~lucid
ros-diamondback-physics-ode (1.4.0-s1298593424~lucid) to 1.4.1-s1306612903~lucid
ros-diamondback-point-cloud-perception (0.5.2-s1299038145~lucid) to 0.5.2-s1306619711~lucid
ros-diamondback-pr2-cockpit (0.3.1-s1302040132~lucid) to 0.3.1-s1306634810~lucid
ros-diamondback-pr2-common (1.4.4-s1299032909~lucid) to 1.4.5-s1306616195~lucid ...
edit retag flag offensive close merge delete


Can you post the error messages you get from roslaunch?
Martin Günther gravatar image Martin Günther  ( 2011-06-08 21:46:10 -0500 )edit
I do not get any errors from roslaunch. Apparently the nodes start up, but then die immediately afterwards. When I do # rosnode list, they are not there. I know they start because one communicates with my robot, and I get the initialization beeps.
chcorbato gravatar image chcorbato  ( 2011-06-08 21:59:12 -0500 )edit
I do not get any errors from roslaunch. Apparently the nodes get disconnected from master, since #rosnode list does not list, but the their processes are still there. Surprisingly killing the roslaunch process in the base machine kills them in the remote ones!
chcorbato gravatar image chcorbato  ( 2011-06-08 21:59:14 -0500 )edit
Maybe its a networking problem? Can you check if each machine can ping the master and vice-versa using the hostname of the machine (not its IP). You can try to set ROS_IP on each machine (to its ip).
dornhege gravatar image dornhege  ( 2011-06-09 00:25:45 -0500 )edit
I don't think it is a network problem, I can ssh from one machine to the other and roslaunch does it: as I said, even killing the roslaunch process in my desktop computer terminates the remote nodes processes in the remote robot computer. The issue is that they do not appear as ROS nodes
chcorbato gravatar image chcorbato  ( 2011-06-09 03:13:44 -0500 )edit
Thank you anyway, I checked what you said :-)
chcorbato gravatar image chcorbato  ( 2011-06-09 03:14:51 -0500 )edit
All implications are that this is a networking issue of some sort, unrelated to roslaunch as the roslaunch processes come up and down correctly. It seems more likely it's a change in a ROS_MASTER_URI, ROS_IP, or some other network configuration as the nodes are having issues contacting the master.
kwc gravatar image kwc  ( 2011-06-09 04:13:43 -0500 )edit
But I did not change any of that configuration. All that changed was upgrade the ros packages. And downgrading them back solved the issue. I agree it is probably not roslaunch as you argue, but maybe some issue with the master?
chcorbato gravatar image chcorbato  ( 2011-06-09 09:48:43 -0500 )edit

1 Answer

Sort by » oldest newest most voted

answered 2011-06-09 03:44:27 -0500

chcorbato gravatar image

Looks like it is an issue with the upgrades in the lucid packages last June 6. I managed to reinstall my ROS installation from the packages in my /var/cache/apt directory and now roslaunch is back working as expected

edit flag offensive delete link more

Question Tools


Asked: 2011-06-07 21:47:57 -0500

Seen: 329 times

Last updated: Jun 09 '11