Robotics StackExchange | Archived questions

roscore has errors

On Unbuntu 12.04, ROS fuerte, in an installation of drcsim-1.3.1 (gazebo), roscore has the following errors (can't have links in post so I Xed those out):

... logging to /home/cga/.ros/log/a6b2c846-60c6-11e2-9f20-0014225a80ab/roslaunch-cga2-2011.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 htXtp:/X/cga2:57907/ ros_comm version 1.8.10

SUMMARY

PARAMETERS * /rosdistro * /rosversion

NODES

auto-starting new master Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Threadblock'",) in ignored process[master]: started with pid [2027] ROSMASTERURI=htXtp:/X/cga2:11311/

setting /runid to a6b2c846-60c6-11e2-9f20-0014225a80ab Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Threadblock'",) in ignored process[rosout-1]: started with pid [2040] started core service [/rosout]

This seems to be causing ROS errors later on. My environment variables are:
ROSROOT=/opt/ros/fuerte/share/ros
ROSLISPPACKAGEDIRECTORY=/opt/ros/fuerte/share/common-lisp/ros
ROSPACKAGEPATH=/home/cga/drc-cmub/ros:/usr/share/drcsim-1.3/ros:/usr/share/drcsim-1.3/models/irobothand:/usr/share/drcsim-1.3/models/golfcart:/usr/share/drcsim-1.3/models/drcterrain:/usr/share/drcsim-1.3/models/sandiahandleft:/usr/share/drcsim-1.3/models/multisensesl:/usr/share/drcsim-1.3/models/sandiahand:/usr/share/drcsim-1.3/models/sandiahandright:/usr/share/drcsim-1.3/models/firehose:/usr/share/drcsim-1.3/models/standpipe:/usr/share/drcsim-1.3/models/atlas:/usr/share/drcsim-1.3/models/powerplant:/usr/share/drcsim-1.3/models/atlassandiahand:/usr/share/drcsim-1.3/models/atlasirobothand:/opt/ros/fuerte/share:/opt/ros/fuerte/stacks
ROSMASTERURI=htXtp:/X/localhost:11311
ROSWORKSPACE=/home/cga/drc-cmub/ros
ROSDISTRO=fuerte
ROSETCDIR=/opt/ros/fuerte/etc/ros

Asked by cga on 2013-01-18 02:03:47 UTC

Comments

Answers

See http://answers.ros.org/question/37087

Meaning other ROS errors later on are likely to have a different cause.

Asked by KruseT on 2013-01-18 02:35:00 UTC

Comments