Gazebo | Ignition | Community
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

"Getting remote endpoint failed" let Gazebo-Gui crash

Hello,

I'm actually trying to install ROS Indigo on a Ubuntu 14.04 machine.

Starting Gazebo ends up in most cases with (4 of 5):

Msg Waiting for masterError [Connection.cc:787] 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

what always ends in:

[gazebo_gui-2] process has died [pid 30325, exit code 134, cmd /opt/ros/indigo/lib/gazebo_ros/gzclient __name:=gazebo_gui __log:=/home/alex/.ros/log/cdde1b80-e1a0-11e3-ab05-5c514ff707c4/gazebo_gui-2.log].
log file: /home/alex/.ros/log/cdde1b80-e1a0-11e3-ab05-5c514ff707c4/gazebo_gui-2*.log

Currently Gazebo 2.2.2 is used which comes via

sudo apt-get install ros-indigo-gazebo-ros

I'm starting Gazebo with

roslaunch gazebo_ros empty_world.launch

This error occurs on both nvidia and intel graphics. Thus, it seems to be independent from hardware.

Has anybody ideas what is going wrong here?

kind regards, Alex

"Getting remote endpoint failed" let Gazebo-Gui crash

Hello,

I'm actually trying to install ROS Indigo on a an Ubuntu 14.04 machine.

Starting Gazebo ends up in most cases with (4 of 5):

Msg Waiting for masterError [Connection.cc:787] 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

what always ends in:

[gazebo_gui-2] process has died [pid 30325, exit code 134, cmd /opt/ros/indigo/lib/gazebo_ros/gzclient __name:=gazebo_gui __log:=/home/alex/.ros/log/cdde1b80-e1a0-11e3-ab05-5c514ff707c4/gazebo_gui-2.log].
log file: /home/alex/.ros/log/cdde1b80-e1a0-11e3-ab05-5c514ff707c4/gazebo_gui-2*.log

Currently Gazebo 2.2.2 is used which comes via

sudo apt-get install ros-indigo-gazebo-ros

I'm starting Gazebo with

roslaunch gazebo_ros empty_world.launch

This error occurs on both nvidia and intel graphics. Thus, it seems to be independent from hardware.

Has anybody ideas what is going wrong here?

kind regards, Alex