search

ros / ros_comm

ROS communications-related packages, including core client libraries (roscpp, rospy, roslisp) and graph introspection tools (rostopic, rosnode, rosservice, rosparam).
http://wiki.ros.org/ros_comm
763 stars 912 forks source link

roslaunch: 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> >' #421

Closed ghost closed 10 years ago

ghost commented 10 years ago

Hi.

I am running Ubuntu 14.04 and have installed ROS from the debs. Everything is installed from scratch. Nothing except the ros-desktop package has been installed.

I want to start Gazebo from ROS as described on the tutorial, using:

$ roslaunch gazebo_ros empty_world.launch

That fails due to the following 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

Not sure if this is the root cause, the full log is bellow. There are strange warnings in the previous log entries.

Not sure if it is related to ROS or Gazebo either. Gazebo looks fine, I can start it without issue.

I have posted a question on the ROS forum:

http://answers.ros.org/question/168856/fails-gazebo-to-start-from-ros-boostexception_detail-error/

This question on the Gazebo forum describes the same issue:

http://answers.gazebosim.org/question/6271/getting-remote-endpoint-failed-let-gazebo-gui/

$ roslaunch gazebo_ros empty_world.launch
... logging to /home/arnaud/.ros/log/251a3d96-e35b-11e3-9539-0016eae586be/roslaunch-hercules-11967.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://hercules:46195/

SUMMARY
========

PARAMETERS
 * /rosdistro: <...>
 * /rosversion: <...>
 * /use_sim_time: True

NODES
  /
    gazebo (gazebo_ros/gzserver)
    gazebo_gui (gazebo_ros/gzclient)

auto-starting new master
process[master]: started with pid [11979]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 251a3d96-e35b-11e3-9539-0016eae586be
process[rosout-1]: started with pid [11992]
started core service [/rosout]
process[gazebo-2]: started with pid [12016]
/opt/ros/indigo/lib/gazebo_ros/gzserver: 5: [: Linux: unexpected operator
process[gazebo_gui-3]: started with pid [12020]
/opt/ros/indigo/lib/gazebo_ros/gzclient: 5: [: Linux: unexpected operator
Gazebo multi-robot simulator, version 2.2.2
Copyright (C) 2012-2014 Open Source Robotics Foundation.
Released under the Apache 2 License.
http://gazebosim.org

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

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
[ INFO] [1400946636.551182005]: Finished loading Gazebo ROS API Plugin.
Msg Waiting for master
[ INFO] [1400946636.557603492]: 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.211
Aborted (core dumped)
[gazebo_gui-3] process has died [pid 12020, exit code 134, cmd /opt/ros/indigo/lib/gazebo_ros/gzclient __name:=gazebo_gui __log:=/home/arnaud/.ros/log/251a3d96-e35b-11e3-9539-0016eae586be/gazebo_gui-3.log].
log file: /home/arnaud/.ros/log/251a3d96-e35b-11e3-9539-0016eae586be/gazebo_gui-3*.log
[ INFO] [1400946637.091142150, 0.022000000]: waitForService: Service [/gazebo/set_physics_properties] is now available.
[ INFO] [1400946637.167613885, 0.093000000]: Physics dynamic reconfigure ready.
^C[gazebo-2] killing on exit
[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done
dirk-thomas commented 10 years ago

Since roslaunch is a Python program the boost exceptions i not coming from there. Since the only node you launched is from gazebo_ros I would suggest filling the ticket in their issue tracker: https://github.com/ros-simulation/gazebo_ros_pkgs

ghost commented 10 years ago

Great. Let's try this.