-
Bug
-
Resolution: Not A Defect
-
Minor
-
None
-
CentOS Linux, version 7
I upgraded from Jenkins 2.319 to 2.320, and all agents failed to start up. I have agents running on Linux, Mac OS, Solaris, and Windows. Below is the error I got.
The work around is to visit every agent and remove the remoting.jar from the previous start up. Without an existing remoting.jar, the agents started up just fine. However, in 2.319 and earlier, I didn't need to manually delete the old file.
java.io.IOException: Could not copy remoting.jar into '/u/build/jenkins/build2' on agent at hudson.plugins.sshslaves.SSHLauncher.copyAgentJar(SSHLauncher.java:715) at hudson.plugins.sshslaves.SSHLauncher.access$300(SSHLauncher.java:112) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:455) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:422) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Caused by: java.lang.IllegalArgumentException: invalid len argument at com.trilead.ssh2.SFTPv3Client.read(SFTPv3Client.java:1232) at com.trilead.ssh2.jenkins.SFTPClient$SFTPInputStream.read(SFTPClient.java:172) at com.google.common.io.ByteStreams.toByteArrayInternal(ByteStreams.java:184) at com.google.common.io.ByteStreams.toByteArray(ByteStreams.java:224) at hudson.plugins.sshslaves.SSHLauncher.readInputStreamIntoByteArrayAndClose(SSHLauncher.java:773) at hudson.plugins.sshslaves.SSHLauncher.copyAgentJar(SSHLauncher.java:684) ... 7 more [11/17/21 19:55:59] Launch failed - cleaning up connection
- is duplicated by
-
JENKINS-67464 Jenkins fails to deploy new remoting.jar file after update to 2.326
- Resolved
-
JENKINS-67258 Could not copy remoting.jar
- Closed