Ask Your Question
1

Seg Fault from Controller Spawner couldn't reach controller_manager to take down controllers. [closed]

asked 2016-11-30 13:34:11 -0500

sauronalexander gravatar image

updated 2016-11-30 15:39:34 -0500

gvdhoorn gravatar image

Hello there, I have encountered troubles when launching controllers, especially joint_trajectory_controller. I got the following log from the terminal:

[INFO] [WallTime: 1480474127.896390] [5.150000] Controller Spawner: Loaded controllers: left_leg_controller, right_leg_controller, head_controller, left_arm_controller, right_arm_controller

Traceback (most recent call last):

  File "/opt/ros/indigo/lib/controller_manager/spawner", line 212, in <module>
    if __name__ == '__main__': main()
  File "/opt/ros/indigo/lib/controller_manager/spawner", line 204, in main
    resp = switch_controller(loaded, [], 2)
  File "/opt/ros/indigo/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 435, in __call__
    return self.call(*args, **kwds)
  File "/opt/ros/indigo/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 525, in call
    raise ServiceException("transport error completing service call: %s"%(str(e)))

**rospy.service.ServiceException: transport error completing service call: unable to receive data from sender, check sender's logs for details**

[INFO] [WallTime: 1480474129.103476] [5.157000] Shutting down spawner. Stopping and unloading controllers...
Segmentation fault (core dumped)

[gazebo-1] process has died [pid 21849, exit code 139, cmd /home/viki/catkin_ws/src/gazebo_ros_pkgs/gazebo_ros/scripts/gzserver -e ode /home/viki/catkin_ws/src/reemc_robot/reemc_simulation/reemc_gazebo/worlds/empty.world __name:=gazebo __log:=/home/viki/.ros/log/aba3bd78-b6a4-11e6-9191-080027b46cdd/gazebo-1.log].
log file: /home/viki/.ros/log/aba3bd78-b6a4-11e6-9191-080027b46cdd/gazebo-1*.log

**[WARN] [WallTime: 1480474160.106558] [5.157000] Controller Spawner couldn't reach controller_manager to take down controllers. Waited for 30 second(s).**

[joint_trajectory_controllers_spawner-3] process has died [pid 21862, exit code 1, cmd /opt/ros/indigo/lib/controller_manager/spawner left_leg_controller right_leg_controller head_controller left_arm_controller right_arm_controller __name:=joint_trajectory_controllers_spawner __log:=/home/viki/.ros/log/aba3bd78-b6a4-11e6-9191-080027b46cdd/joint_trajectory_controllers_spawner-3.log].
log file: /home/viki/.ros/log/aba3bd78-b6a4-11e6-9191-080027b46cdd/joint_trajectory_controllers_spawner-3*.log

^C[head_controller/point_head_action-4] killing on exit
[gazebo_gui-2] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete

Can anyone figure what might be the problem of this issue? I am using Gazebo7 and ROS Indigo. Thank you very much!

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by 130s
close date 2017-05-18 19:25:32.084135

Comments

Now I have shifted back to Gazebo2. ROS seems have loaded the controllers correctly but cannot start the controllers.

sauronalexander gravatar image sauronalexander  ( 2016-12-01 14:53:27 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2016-12-06 22:57:36 -0500

sauronalexander gravatar image

Reinstalling ROS solves the entire problem.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2016-11-30 13:34:11 -0500

Seen: 276 times

Last updated: Dec 06 '16