Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

issues launching Gazebo

asked 2016-09-04 21:26:33 -0500

tenichols
1 ●1 ●1 ●1

updated 2016-09-05 01:49:00 -0500

gvdhoorn
86574 ●283 ●1432 ●1054 http://cor.tudelft.nl/

I am getting this response in the terminal when attempting to run Gazebo. Does anyone have any idea what is going on and how I may resolve the problem.

[gazebo-2] process has died [pid 2687, exit code 139, cmd /opt/ros/indigo/lib/gazebo_ros/gzserver -e ode /home/tenicho/ros_ws/src/baxter_simulator/baxter_gazebo/worlds/baxter.world __name:=gazebo __log:=/home/tenicho/.ros/log/5b625bd4-730c-11e6-89ca-08002710caa1/gazebo-2.log].
log file: /home/tenicho/.ros/log/5b625bd4-730c-11e6-89ca-08002710caa1/gazebo-2*.log

[INFO] [WallTime: 1473040769.872637] [0.093000] Calling service /gazebo/set_model_configuration
Service call failed: unable to connect to service: [Errno 111] Connection refused

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2016-09-05 02:51:38 -0500

gvdhoorn
86574 ●283 ●1432 ●1054 http://cor.tudelft.nl/

139 could be a SEGFAULT (128 + 11). Common causes for gazebo to SEGFAULT: running in a VM, not having proper/correct 3D hw drivers installed, (unstable) CPU overclocks, etc. The second error is just telling you that something is calling a service that doesn't exist anymore.

edit flag offensive delete link

add a comment

Question Tools

1 follower

Stats

Asked: 2016-09-04 21:26:33 -0500

Seen: 471 times

Last updated: Sep 05 '16

issues launching Gazebo edit

1 Answer

Question Tools

Stats

Related questions

issues launching Gazebo