-
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
-
Seeing the same issue with agent startup (Could not copy remoting.jar / invalid len argument).
Jenkins updated yesterday to 2.321 (cannot tell from which version).
After instance restart all nodes are down with log as above. Some nodes can be started after deleting remoting.jar from their folder, some show no improvement.
Worth noting that agent-roots are on nfs. Permissions have not changed recently and look to be in line. And most nodes do get working.
The permanently failing nodes are debian9,centos7. However, some centos7 nodes come up. Centos8 come up.
{{
[11/18/21 18:03:50] [SSH] Checking java version of java
[11/18/21 18:03:50] [SSH] java -version returned 1.8.0_242.
[11/18/21 18:03:50] [SSH] Starting sftp client.
[11/18/21 18:03:51] [SSH] Copying latest remoting.jar...
java.io.IOException: Could not copy remoting.jar into '/home/xcb-jenkins-onload/agent-roots/dellr210t' 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.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
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/18/21 18:03:51] Launch failed - cleaning up connection
[11/18/21 18:03:51] [SSH] Connection closed.
}}