A recent update broke Gazebo for me in ROS Groovy. Where do I post the problem and what information should I include? [closed]

asked 2014-04-09 05:12:28 -0600

RigorMortis gravatar image

The problem started yesterday (April 8, 2014) and I believe the guilty update is 'ros-groovy-gazebo-ros-current' but I can't be completely sure since many updates happened at the same time.

Running any gazebo launch file from ROS except the 'empty_world.launch' results in errors and an empty gazebo window. Running my launch file (which has worked for weeks previous to yesterday) results in this output:

ROS_MASTER_URI=http://localhost:11311

core service [/rosout] found process[gazebo-1]: started with pid [8252] process[gazebo_gui-2]: started with pid [8260] process[spawn_smaug-3]: started with pid [8271]

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

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

process[spawn_ramp1-4]: started with pid [8286]

Msg Waiting for master

Msg Waiting for masterprocess[spawn_ramp2-5]: started with pid [8311]

[ INFO] [1397055901.852148927]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...  [1;32Msgm MsgConnected to gazebo master @ http://127.0.0.1:11345Connected to gazebo master @ http://127.0.0.1:11345

Msg[1; Publicized address: 32129.107.182.16m

Msg Publicized address: 129.107.182.16

loading model xml from ros parameter

[INFO] [WallTime: 1397055902.297228] [0.000000] waiting for service /gazebo/spawn_urdf_model loading model xml from ros parameter

[INFO] [WallTime: 1397055902.335058] [0.000000] waiting for service /gazebo/spawn_urdf_model

Service call failed: unable to connect to service: [Errno 104] Connection reset by peer

Service call failed: transport error completing service call: unable to receive data from sender, check sender's logs for details

Segmentation fault (core dumped)

[gazebo-1] process has died [pid 8252, exit code 139, cmd /opt/ros/groovy/stacks/simulator_gazebo/gazebo/scripts/gazebo -u /opt/ros/groovy/stacks/simulator_gazebo/gazebo_worlds/worlds/empty.world __name:=gazebo __log:=/home/emrysm/.ros/log/9caa95c0-bff4-11e3-9830-74e50b1cfbaa/gazebo-1.log].

log file: /home/emrysm/.ros/log/9caa95c0-bff4-11e3-9830-74e50b1cfbaa/gazebo-1*.log

loading model xml from ros parameter

[INFO] [WallTime: 1397055902.447661] [0.000000] waiting for service /gazebo/spawn_urdf_model

[spawn_smaug-3] process has finished cleanly

log file: /home/emrysm/.ros/log/9caa95c0-bff4-11e3-9830-74e50b1cfbaa/spawn_smaug-3*.log

[spawn_ramp1-4] process has finished cleanly

log file: /home/emrysm/.ros/log/9caa95c0-bff4-11e3-9830-74e50b1cfbaa/spawn_ramp1-4*.log

[gazebo_gui-2] process has finished cleanly

log file: /home/emrysm/.ros/log/9caa95c0-bff4-11e3-9830-74e50b1cfbaa/gazebo_gui-2*.log

edit retag flag offensive reopen merge delete

Closed for the following reason Gazebo Question: The Gazebo community prefers to answer questions at: http://answers.gazebosim.org by tfoote
close date 2018-01-30 22:51:04.839978

Comments

You should ask this question on answers.gazebosim.org

SL Remy gravatar image SL Remy  ( 2014-04-09 08:43:24 -0600 )edit

Thanks - I posted it there as well.

RigorMortis gravatar image RigorMortis  ( 2014-04-09 14:20:43 -0600 )edit