Which typically happens when the SSH server has "bogged down" and is processing requests really slowly.
So, IMHO, the right thing to do is instead of re-trying ... is to back off the attempt and idle until the SSH server becomes less busy.
If I'm right:
* you'll only see this on boxen under heavy load
* you'll not see this on boxen with light load
* you'll be able to relieve the problem by slowing down the boxen acting as clients.
Just so summarize what I'm seeing here... the root cause is:
raise SSHException('Error reading SSH protocol banner' + str(x))
Which typically happens when the SSH server has "bogged down" and is processing requests really slowly.
So, IMHO, the right thing to do is instead of re-trying ... is to back off the attempt and idle until the SSH server becomes less busy.
If I'm right:
* you'll only see this on boxen under heavy load
* you'll not see this on boxen with light load
* you'll be able to relieve the problem by slowing down the boxen acting as clients.