csshx
csshx copied to clipboard
brockgr
csshX fails to open shells to some hosts when using large clusters
What steps will reproduce the problem?
1. csshX -debug 1 -l usernamename sshbastionserver host2 host3 host4 host5
host6 host7 host 8 host9 host10 host 11 host12 host13 host14 host15 host16
host17
2. my .ssh/config contains:
Host host*
ProxyCommand ssh username@sshbastionserver exec nc %h %p
User username
ForwardAgent yes
What is the expected output? What do you see instead?
error given is
(for each of host14 host15 host16 host17)
e.g. host14:
ssh -l username host14
ssh_exchange_identification: Connection closed by remote host
ssh_exchange_identification: Connection closed by remote host
CHILD at /usr/local/bin/csshX line 1241.
What version of csshX (do a "csshX -v") are you using? On what operating
system version?
csshX v0.73-178
and
csshX v0.73-169
(same result)
OSX 10.6.8
Please provide any additional information below.
Testing with other hosts and not using any .ssh/config gives the same result.
Original issue reported on code.google.com by mike.forbes on 28 Jun 2011 at 9:03
Just to check, if you try to connect to the server on the command line (e.g.
"ssh -l username host14"), will it connect fine?
How about just "csshX -debug 1 -l usernamename host14 host15 host16 host17" ?
The ssh_exchange_identification message is from ssh, not csshX. If the hosts
14~17 are working correctly for normal ssh, then maybe you are hitting some
limit on the proxying through sshbastionserver.
Original comment by gavin.brock on 28 Jun 2011 at 11:49
Yep I can connect fine to the hosts using regular ssh, and if I try to connect
to the failed hosts with csshX it works.
all at once it doesn't work.
I'll check with a coworker who's not using a mac (but is using cluster-ssh) to
see if it's some sort of weird limitation by nc or ProxyCommand
Original comment by mike.forbes on 28 Jun 2011 at 11:58
I have this same issue. I also connect using a bastion server and am trying to
csshx into 16 servers. Sometimes it connects to all 16 servers and sometimes it
doesn't. When it doesn't, I close all the terminal windows and try again.
Original comment by [email protected] on 23 Dec 2011 at 4:07
I have the same issue on 15+ servers. It is usually the tail end of the
servers I have in the list. Could this be that it's trying to open the SSH
windows to quickly?
Original comment by [email protected] on 22 Mar 2013 at 3:15
This still seems to be happening for me using the same type of configuration
through an ssh proxy host. The issue doesn't occur when using cluster-ssh on my
linux box.
Original comment by [email protected] on 5 Jun 2014 at 8:37
Same issue here on Mac going to bastion server. Any chance to get this fixed?
