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

Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

0

rocon: 'already connected to this hub'

asked 2014-08-25 22:36:43 -0500

bjem85
163 ●21 ●25 ●33

Hi,

I am following through the roscon installation tutorial for ROS Hydro, but I am getting stuck at the verification step.

The instructions say to execute:

> . /opt/ros/hydro/setup.bash
> rocon_launch chatter_concert chatter.concert

When I do this the terminal windows spawn as expected. However they all have a warning:

[WARN] [WallTime: 1409023936.036277] Gateway : not registering on the hub [already connected to this hub]
[WARN] [WallTime: 1409023936.544642] Gateway : not registering on the hub [already connected to this hub]

Is this warning a problem or not? The hub seems to be running as though it's a daemon, as closing the terminal down and starting this command again does not make the warning go away.

I would post a screen shot but I don't have enough points (need at least 20) to do so.

Kind Regards Bart

edit retag flag offensive close merge delete

Comments

I don't know about this message in particular, but warnings generally imply that a given operation worked, although something was noticed in passing.

joq ( 2014-08-27 14:42:22 -0500 )edit

1 Answer

Sort by » oldest newest most voted

1

answered 2014-09-10 21:58:24 -0500

Daniel Stonier
3145 ●24 ●51 ●64

Ok, digging back through my memory, I believe this is because it was starting a gateway with default settings to look for a hub on localhost, and also via zeroconf. If the localhost hub was found (which it did for chatter_concert), then zeroconf discovery would throw this warning when it would discover the same hub.

This has been updated on the hydro-devel/indigo branches so that it doesn't do this double lookup.

In short, don't worry about it :)

edit flag offensive delete link

Comments

I haven't verified this but it sounds reasonable.

bjem85 ( 2014-09-16 03:51:58 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2014-08-25 22:36:43 -0500

Seen: 130 times

Last updated: Sep 10 '14

Related questions

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.

Powered by Askbot version 0.10.2