In general, this condition only happens if there is a network
misconfiguration issue. The fact that tools like roswtf and other
utilities cannot connect to the master imply this as well. You may
want to check this list for common issues:
http://www.ros.org/wiki/ROS/Troubleshooting
You should never have to specify the run-id manually. As above, there
is likely a network issue.
- Ken
On Tue, Aug 17, 2010 at 8:19 AM, Max B <
skinkworks42@gmail.com> wrote:
> Hello,
> I am using the cturtle Ubuntu repositories for Lucid. When I run
> roscore, if I start a roslaunch instance in another terminal, it fails with
> "run_id on parameter server does not match declared run_id:
> b6c96aa0-aa11-11df-96c8-001d92f61800 vs
> c59dc274-aa11-11df-8038-001d92f61800". If I manually specify the runid, it
> works fine. ROS_IP is empty, and ROS_MASTER_URI is "http://localhost:11311".
> Everything works fine, however, if I do not start roscore manually and I let
> it start with roslaunch. What is wrong? In addition, roswtf and other
> utilities cannot connect to the master.
> From,
> Max
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>
(text/plain)