| I doubt the encode sequence values are a reliable differentiator. I searched for the message and there are very few instances of it. The few that exist are mostly connected with Windows and / or Bitvise. Those seem to be the commonalities. There has been a long history of connection issues generally with SSH servers on Windows. Yes, the ssh-slaves-plugin uses a forked version of the trilead ssh library instead of the jsch one. So that one may not be relevant. I'm afraid I don't have any good suggestions for troubleshooting / debugging this. It kind of looks like this has some relation to the SSH transport. The only instances of this error are connected to SSH agents and your experience using a different SSH server show distinct variations in results. The trick is probably to figure out what it is about the SSH transport that is introducing the problem. The logs you provided only show information at the upper, remoting level and are insufficient to get further. You could try using Wireshark or some other network capture tool. That gives such low-level results that it's hard to sort through it and isolate the specific issue. You might be able to figure something out from it, though. |
