Home | Tutorials | Wiki | Issues
Ask Your Question
1

Spawning URDF in Hydro, Gazebo 1.9 has (core dumped) issue

asked 2013-09-15 10:10:25 -0600

ncr7 gravatar image

So I went through and installed hydro to see if I can get around my issues I'm having with getting Groovy to work with Gazebo...

So far, I can't seem to get urdf files to load in Gazebo without it crashing.

I followed the Hydro instructions on ROS's website, I then installed Gazebo 1.9 from the Gazebo website.
I made sure Gazebo was running properly, by doing,

roslaunch gazebo_ros empty_world.launch

Gazebo starts up with no issues.

I then open another terminal and run from this tutorial,

(Note: already downloaded git clone https://github.com/RethinkRobotics/ba...)

rosrun gazebo_ros spawn_model -file `rospack find baxter_description`/urdf/baxter.urdf -urdf -z 1 -model baxter

After running spawn_model I get the following error in the terminal,

master@WALL-E:~/hydro_workspace/catkin_ws$ rosrun gazebo_ros spawn_model -file `rospack find baxter_description`/urdf/baxter.urdf -urdf -z 1 -model baxter
spawn_model script started
[INFO] [WallTime: 1379256713.542766] [11.162000] Loading model xml from file
[INFO] [WallTime: 1379256713.544657] [11.164000] Waiting for service /gazebo/spawn_urdf_model
[INFO] [WallTime: 1379256713.549477] [11.169000] Calling service /gazebo/spawn_urdf_model
Service call failed: transport error completing service call: unable to receive data from sender, check sender's logs for details

I then looked back at the terminal I ran Gazebo's empty_world.launch and see,

master@WALL-E:/opt/ros/hydro/share$ roslaunch gazebo_ros empty_world.launch 
... logging to /home/master/.ros/log/545a3300-1e16-11e3-91ec-648099728e34/roslaunch-WALL-E-2734.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 http://WALL-E:38925/

SUMMARY
========

PARAMETERS
 * /rosdistro
 * /rosversion
 * /use_sim_time

NODES
  /
    gazebo (gazebo_ros/gzserver)
    gazebo_gui (gazebo_ros/gzclient)

auto-starting new master
process[master]: started with pid [2748]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 545a3300-1e16-11e3-91ec-648099728e34
process[rosout-1]: started with pid [2763]
started core service [/rosout]
process[gazebo-2]: started with pid [2778]
process[gazebo_gui-3]: started with pid [2783]
Gazebo multi-robot simulator, version 1.9.0
Copyright (C) 2013 Open Source Robotics Foundation.
Released under the Apache 2 License.
http://gazebosim.org

Gazebo multi-robot simulator, version 1.9.0
Copyright (C) 2013 Open Source Robotics Foundation.
Released under the Apache 2 License.
http://gazebosim.org

Msg Waiting for master.[ INFO] [1379256701.427472924]: Finished loading Gazebo ROS API Plugin.
Msg Waiting for master[ INFO] [1379256701.429640946]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...

Msg Connected to gazebo master @ http://127.0.0.1:11345
Msg Publicized address: 192.168.1.8

Msg Connected to gazebo master @ http://127.0.0.1:11345
Msg Publicized address: 192.168.1.8
[ INFO] [1379256702.348180490, 0.024000000]: waitForService: Service [/gazebo/set_physics_properties] is now available.
[ INFO] [1379256702.402423363, 0.073000000]: Physics dynamic reconfigure ready.
terminate called after throwing an instance of 'std::ios_base::failure'
  what():  basic_ios::clear
Aborted (core dumped)
[gazebo-2] process has died [pid 2778, exit code 134, cmd /opt/ros/hydro/lib/gazebo_ros/gzserver worlds/empty.world __name:=gazebo __log:=/home/master/.ros/log/545a3300-1e16-11e3-91ec-648099728e34/gazebo-2.log].
log file: /home/master/.ros/log/545a3300-1e16-11e3-91ec-648099728e34/gazebo-2 ...
(more)
edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted
0

answered 2013-09-15 21:52:47 -0600

ncr7 gravatar image

If you happen to be getting this error, uninstall and reinstall from source. I uninstalled Groovy 1.9 debian install and re-installed from source and now I don't get the (core dumped) issue.

edit flag offensive delete link more

Comments

Has this been confirmed as a "general" solution by others?

Rasmus gravatar imageRasmus ( 2013-09-20 05:59:58 -0600 )edit

I haven't seen any other issues with it. I know it worked for me though.

ncr7 gravatar imagencr7 ( 2013-09-24 17:22:19 -0600 )edit

I have the same problem, I tried to reinstall but it did not help.

Wojciech gravatar imageWojciech ( 2013-09-25 18:04:20 -0600 )edit

I know I spent a bit of time uninstalling and re-installing. I finally removed all ros-packages, "sudo apt-get remove ros-", and "sudo apt-get remove gazebo". After this is when I seemed to have success. I don't know if this will work for you, but I think having fuerte installed even without it linked in the .bashrc seemed to cause an install problem.

ncr7 gravatar imagencr7 ( 2013-10-01 00:27:00 -0600 )edit
0

answered 2013-10-01 01:47:50 -0600

Wojciech gravatar image

Try:

killall gzserver

then:

LANG="C"

In the end it worked.

edit flag offensive delete link more
Login/Signup to Answer

Question Tools

1 follower

Stats

Asked: 2013-09-15 10:10:25 -0600

Seen: 1,537 times

Last updated: Oct 01 '13