ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

"Incompatible ssh peer" when launching a remote node

asked 2016-12-18 01:16:03 -0500

vinmean gravatar image

I want to launch a node on a remote embedded system from my PC. My PC happens to run ROS indigo and the embedded platform runs ROS Kinetic. I made a launch file to run remote node.

<machine name = "tegra-ubuntu" address="" user="ubuntu" env-loader="/opt/ros/kinetic/"/>
<node machine="tegra-ubuntu" name="ego_motion" pkg="ego_motion" type="odom_listener_node"/>

When I do a ros launch from the host system to this remote system I get the following error

deepak@sword:~/workspace/ROS_Workspace/iruVizhi_v1/src/remote/launch$ roslaunch remote remote.launch 
... logging to /home/deepak/.ros/log/ff8de646-c4e3-11e6-a1a7-ac7ba196454c/roslaunch-sword-18118.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
remote[] starting roslaunch
remote[]: creating ssh connection to, user[ubuntu]
remote[]: failed to launch on tegra-ubuntu:

Unable to establish ssh connection to [ubuntu@]: Incompatible ssh peer (no acceptable kex algorithm)

[] killing on exit
unable to start remote roslaunch child:
The traceback for the exception was written to the log file

I get this "Incompatible ssh peer (no acceptable kex algorithm)" error. Is there a fix for this problem? Is it because I use ROS Indigo and Kinetic on these machines?

edit retag flag offensive close merge delete



This isn't really related to ROS. I did a quick google search, and the results seem to suggest that it happens because the python SSH library (paramiko) in Ubuntu 14.04 (since you're using Indigo I'm guessing you have Ubuntu 14.04) can't connect to newer SSH servers (Ubuntu 15.10 and newer)

ahendrix gravatar image ahendrix  ( 2016-12-18 02:00:56 -0500 )edit

Yes, what @ahendrix writes is most likely the cause here. I seem to remember having seen (multiple) questions about this already here on ROS Answers, but can't find them again. Until someone updates/upgrades the SSH library used by roslaunch, this is going to stay a problem.

gvdhoorn gravatar image gvdhoorn  ( 2016-12-18 05:02:54 -0500 )edit

Thanks for the comment. Yes, you were right. The PC was running 14.04 and the embedded device was running 16.04.

vinmean gravatar image vinmean  ( 2016-12-18 17:18:55 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2016-12-18 16:59:19 -0500

vinmean gravatar image

I upgraded paramiko to fix this problem

sudo pip install paramiko --upgrade
edit flag offensive delete link more


Just to be clear, which device did you upgrade paramiko, the PC or the embedded platform?

jbourne gravatar image jbourne  ( 2017-01-04 16:13:06 -0500 )edit

I upgraded paramiko on the PC

vinmean gravatar image vinmean  ( 2017-01-04 17:21:49 -0500 )edit

Question Tools

1 follower


Asked: 2016-12-18 01:16:03 -0500

Seen: 2,240 times

Last updated: Dec 18 '16