Gazebo PR2 getting stuck at launch
When I run empty world, everything seems to be fine.
roslaunch gazebo_worlds empty_world.launch
But when I instead try to bring up PR2 in gazebo, it gets stuck in both Fuerte and Groovy. (Update to Groovy since things were getting stuck but getting stuck the same way) This is running on Ubuntu 12.04. This is not working with lastest copy of Groovy on two different computers both running 12.04 64-bit. Also purging all ROS related stuff and reinstalling (Fuerte and Groovy) didn't help at all.
roslaunch pr2_gazebo pr2.launch
It gets stuck with following warnings. Please help!
process[robot_pose_ekf-17]: started with pid [18327]
process[base_hokuyo_node-18]: started with pid [18366]
process[tilt_hokuyo_node-19]: started with pid [18416]
process[tf2_buffer_server-20]: started with pid [18473]
[ WARN] [1357828826.779339967]: You've passed in true for auto_start for the C++ action server at [/tf2_buffer_server]. You should always pass in false to avoid race conditions.
process[camera_synchronizer_node-21]: started with pid [18498]
[ INFO] [1357828826.995402836]: Starting to spin camera_synchronizer at 100.000000 Hz...
process[default_controllers_spawner-22]: started with pid [18568]
process[r_gripper_controller/gripper_action_node-23]: started with pid [18570]
process[l_gripper_controller/gripper_action_node-24]: started with pid [18599]
process[head_traj_controller/point_head_action-25]: started with pid [18648]
process[torso_controller/position_joint_action_node-26]: started with pid [18695]
[ WARN] [1357828831.245960240]: The input topic '/wide_stereo/left/image_raw' is not yet advertised
[ WARN] [1357828831.246159850]: The input topic '/wide_stereo/left/camera_info' is not yet advertised
[ WARN] [1357828831.246197213]: The input topic '/wide_stereo/right/image_raw' is not yet advertised
[ WARN] [1357828831.246220592]: The input topic '/wide_stereo/right/camera_info' is not yet advertised
[ WARN] [1357828831.416542110]: The input topic '/narrow_stereo/left/image_raw' is not yet advertised
[ WARN] [1357828831.416826507]: The input topic '/narrow_stereo/left/camera_info' is not yet advertised
[ WARN] [1357828831.417022828]: The input topic '/narrow_stereo/right/image_raw' is not yet advertised
[ WARN] [1357828831.417143055]: The input topic '/narrow_stereo/right/camera_info' is not yet advertised
[ WARN] [1357828831.455619028]: The input topic '/narrow_stereo/left/image_raw' is not yet advertised
[ WARN] [1357828831.455817538]: The input topic '/narrow_stereo/left/camera_info' is not yet advertised
[ WARN] [1357828831.455872881]: The input topic '/narrow_stereo/right/image_raw' is not yet advertised
[ WARN] [1357828831.455923623]: The input topic '/narrow_stereo/right/camera_info' is not yet advertised
[ WARN] [1357828891.249665241]: The input topic '/wide_stereo/left/image_raw' is not yet advertised
[ WARN] [1357828891.249748211]: The input topic '/wide_stereo/left/camera_info' is not yet advertised
[ WARN] [1357828891.249790211]: The input topic '/wide_stereo/right/image_raw' is not yet advertised
[ WARN] [1357828891.249831981]: The input topic '/wide_stereo/right/camera_info' is not yet advertised
[ WARN] [1357828891.420719083]: The input topic '/narrow_stereo/left/image_raw' is not yet advertised
[ WARN] [1357828891.420869955]: The input topic '/narrow_stereo/left/camera_info' is not yet advertised
[ WARN] [1357828891.421049482]: The input topic '/narrow_stereo/right/image_raw' is not yet advertised
[ WARN] [1357828891.421141085]: The input topic '/narrow_stereo/right/camera_info' is not yet advertised
[ WARN] [1357828891.456356647]: The input topic '/narrow_stereo/left/image_raw' is not yet advertised
[ WARN] [1357828891.456442792]: The input topic '/narrow_stereo/left/camera_info' is not yet advertised
[ WARN] [1357828891.456691924]: The input topic '/narrow_stereo/right/image_raw' is not yet ...
I am having a hard time reproducing it. If you did
ps -ef | grep gz
do you still see gzclient or gzserver running? If so, can you attach a gdb session to them, and post the result of
thread apply all bt?
thanks.
I really appreciate you are trying to help. It has been very frustrating last few days since it worked fine back in October. All I did was update to latest ros/gazebo. I added more info in the question. So gzclient is running when pr2emptyworld.launch is used.
I attached gdb but not sure how I can give you anything useful. (new to gdb). Typed "backtrace" but shows nothing.
can you try this?
roslaunch gazebo_worlds debug.launch
and see if it segfaults and bring you to the (gdb) prompt? If so, type:
thread apply all bt
and post the result. thanks.
roslaunch gazeboworlds debug.launch did not bring me into gdb prompt. So, I just attached gdb to pr2emptyworld.launch and ran backtrace and thread apply all bt as you suggested before. Thanks for help! I really need this working and it is odd since it is not working with both computers I have.
The backtrace you've provided is for the gazebo client gui, but what we need here is a backtrace of the server when it goes down. Did
roslaunch gazebo_worlds debug.launch
bring up gazebo with an empty world successfully?
Yes gazeboworlds debug.launch brought up successfully... didn't bring me into gdb. It is whenever I try to launch pr2.launch or pr2emptyworld.launch than it fails. When pr2_emptyworld goes down only the client is left. server is dead.. what should I try next? ... Thanks!
I was finally able to attach gdb to gzserver which dies very quickly. Please see above. Thank you.
the error you posted trying to compile pr2_gazebo seems to indicate
sudo apt-get install ros-groovy-pr2-simulator
did not completed successfully in your previous installs. But for now you can do:
sudo apt-get install ros-groovy-orocos-kdl
and try to recompile
Hsu, that didn't help. I summarized above what I have tried so far.. Hsu, is there any direct email I can discuss this issue? It is becoming very frustrating and this is huge blocker for me..