Gazebo | Ignition | Community
Ask Your Question

Gazebo Crashes When Launching Through ROS

asked 2014-06-09 16:56:52 -0500

K. Zeng gravatar image

updated 2014-06-10 12:59:25 -0500

scpeters gravatar image

Hi everyone. I've been trying to follow along this tutorial: I use Gazebo 2.2.2 with ROS Indigo and Ubuntu 14.04. The problem is that whenever I use roslaunch, there is a greater than 50% chance that the GUI will crash. The relevant printouts are below, with what I think are the important parts in bold:

Msg Waiting for master**Error [] Getting remote endpoint failed
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'**
  what():  remote_endpoint: Transport endpoint is not connected
[ INFO] [1402350507.784227963]: Finished loading Gazebo ROS API Plugin.
Msg Waiting for master
[ INFO] [1402350507.788051043]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
Msg Connected to gazebo master @
Msg Publicized address:
Aborted (core dumped)
**[gazebo_gui-3] process has died [pid 8125, exit code 134, cmd /opt/ros/indigo/lib/gazebo_ros/gzclient __name:=gazebo_gui __log:=/home/s/.ros/log/c94fe566-f01f-11e3-a690-001aa0adcadc/gazebo_gui-3.log].**
log file: /home/s/.ros/log/c94fe566-f01f-11e3-a690-001aa0adcadc/gazebo_gui-3*.log
[ INFO] [1402350509.082584759, 0.022000000]: waitForService: Service [/gazebo/set_physics_properties] is now available.
[ INFO] [1402350509.157011114, 0.089000000]: Physics dynamic reconfigure ready.

I know this question has already been asked in as well as, and someone suggested a workaround in However, the workaround did not help at all in my case, and I didn't find any other solutions. Any help from fellow users here would be greatly appreciated. Thanks.

NOTE: I'm very sorry about the format. I'm new to this, and I can't quite figure out how to separate paragraphs in this format.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2014-06-10 13:07:58 -0500

scpeters gravatar image

The remote endpoint failed to connect is being tracked in issue 1204. We don't have a solution yet, but it appears to be a problem with gazebo's transport layer between gzserver and gzclient. Try running headless (without gzclient) and see if that works.

edit flag offensive delete link more


I just ran gzserver by first launching roscore, then used the command "rosrun gazeboros gzserver". There are no issues there aside from the line "/opt/ros/indigo/lib/gazeboros/gzserver: 5: [: Linux: unexpected operator". I've killed and restarted gzserver several times and did not encounter the "Getting remote endpoint failed" error.

K. Zeng gravatar imageK. Zeng ( 2014-06-10 13:46:50 -0500 )edit

You should be able to launch gzclient separately as well, once gzserver is running properly.

scpeters gravatar imagescpeters ( 2014-06-10 13:50:52 -0500 )edit

I was able to launch gzclient with "rosrun gazeboros gzclient" once gzserver was up. Again, there were no issues aside from the line "/opt/ros/indigo/lib/gazeboros/gzclient: 5: [: Linux: unexpected operator" in the console. I've also noticed that the error happens far more often when I use roslaunch than when I use roscore and then rosrun.

K. Zeng gravatar imageK. Zeng ( 2014-06-10 13:53:53 -0500 )edit
Login/Signup to Answer

Question Tools



Asked: 2014-06-09 16:56:52 -0500

Seen: 2,052 times

Last updated: Jun 10 '14