roslaunch -v drcsim_gazebo atlas.launch fails

asked 2013-12-20 17:22:58 -0600

Nicu Tofan gravatar image

I've just installed gazebo-current and drcsim on an Ubuntu 13.10 64-bit system, but the command that I've mentioned in title

roslaunch -v drcsim_gazebo atlas.launch

shows gazebo misbehaving. On first run I get:

setting /run_id to d37bc118-69c4-11e3-909e-00e052b4d2d5
process[rosout-1]: started with pid [2927]
started core service [/rosout]
process[gazebo-2]: started with pid [2930]
process[atlas_robot_state_publisher-3]: started with pid [2932]
process[multisense_sl_robot_state_publisher-4]: started with pid [2933]
process[tf2_buffer_server-5]: started with pid [2934]
process[multisense_sl/camera/stereo_proc-6]: started with pid [2935]
[ INFO] [1387577990.782963156]: Finished loading Gazebo ROS API Plugin.
terminate called after throwing an instance of 'boost::thread_interrupted'
Warning [gazebo_main.cc:94] escalating to SIGKILL on client
[gazebo-2] process has finished cleanly
log file: ~/.ros/log/d37bc118-69c4-11e3-909e-00e052b4d2d5/gazebo-2*.log
^C[multisense_sl/camera/stereo_proc-6] killing on exit
[tf2_buffer_server-5] killing on exit
[multisense_sl_robot_state_publisher-4] killing on exit
[atlas_robot_state_publisher-3] killing on exit
[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done

on second run I get

auto-starting new master
process[master]: started with pid [4505]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to cc958ef0-69ca-11e3-a096-00e052b4d2d5
process[rosout-1]: started with pid [4518]
started core service [/rosout]
process[gazebo-2]: started with pid [4530]
process[atlas_robot_state_publisher-3]: started with pid [4532]
process[multisense_sl_robot_state_publisher-4]: started with pid [4534]
process[tf2_buffer_server-5]: started with pid [4550]
process[multisense_sl/camera/stereo_proc-6]: started with pid [4597]
[ INFO] [1387580550.851402860]: Finished loading Gazebo ROS API Plugin.
terminate called after throwing an instance of 'boost::thread_interrupted'
Error [ConnectionManager.cc:123] Connection Manager is not running
[gazebo-2] process has finished cleanly
log file: ~/.ros/log/cc958ef0-69ca-11e3-a096-00e052b4d2d5/gazebo-2*.log
^C[multisense_sl/camera/stereo_proc-6] killing on exit
[tf2_buffer_server-5] killing on exit
[multisense_sl_robot_state_publisher-4] killing on exit
[atlas_robot_state_publisher-3] killing on exit
[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done

The file ~/.ros/log/cc958ef0-69ca-11e3-a096-00e052b4d2d5/gazebo-2*.log does not exists.

I can run gzserver & gzclient without any problem, except that gzclient has a segmentation fault after I close it from the GUI.

dpkg -s gazebo | grep 'Version'
Version: 1.9.2-1~saucy
Config-Version: 1.9.2-1~saucy

dpkg -s drcsim | grep 'Version'
Version: 3.1.1-2~quantal
edit retag flag offensive close merge delete