Gazebo | Ignition | Community
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

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

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/baxter_common.git)

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*.log

I tried looking at log file /home/master/.ros/log/545a3300-1e16-11e3-91ec-648099728e34/gazebo-2*.log but it was not written to the specified location...

Any ideas as to what is happening here?