[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down

[j...@keyba.se (JIRA)]

Title: Message Title

John Zila commented on JENKINS-53468   Re: Since 1.27 update Channel is closing or has closed down Which Jenkins core version do you use? Jenkins 2.141 Which OS do you use on your SSH agents? Debian Jessie. admin@ip-10-0-0-211:~$ uname -a Linux ip-10-0-0-211 4.9.0-0.bpo.6-amd64 #1 SMP Debian 4.9.88-1+deb9u1~bpo8+1 (2018-05-13) x86_64 GNU/Linux Which OpenSSH version do you have installed on your SSH agents? admin@ip-10-0-0-211:~$ ssh -V OpenSSH_6.7p1 Debian-5+deb8u4, OpenSSL 1.0.1t 3 May 2016 Do it happen only on the SSH agents? yes Do it happen on all SSH agents or only on a few? Is there something in common between those SSH agents? randomly, most of them Are your SSH agents static or provisioned by a cloud plugin (k8s, Mesos, Docker, EC2, Azure, ...)? EC2 spot fleet plugin Could you attach the agent connection log (JENKINS_URL/computer/NODENAME/log)? No, because I'd have to switch my cluster to use the broken plugin Could you attach the logs inside the remoting folder (see https://github.com/jenkinsci/remoting/blob/master/docs/workDir.md#remoting-work-directory)?  No, as above I'd have to switch my cluster to use the broken plugin Could you attach the agent configuration (JENKINS_URL/computer/NODENAME/config.xml) file? attached config.xml Do you see if it happens always with the same job or type of job? any job Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.