SSH Build Agent is 1.31.2. Trilead-api is 1.0.13. It only happens once the server gets reboot. It'll be chugging along for a few weeks fine, then as soon as the server gets reboot after the latest OS patches have been applied, I'll have to delete the remoting.jar file again. A bit frustrating.
On Wednesday, March 30, 2022 at 4:07:35 PM UTC-6 [email protected] wrote: > I do not really have too much data to know what exactly is going on, which > version of the SSH build Agents and the trilead-api plugins are you using? > Are you using the latest versions? Do the issue happen only in that agent? > Which SSH server do you use and what version? Do you have any kind of > transfer limit on that agent? my theory is that the sftp read operation > fail because something cut it. > > El miércoles, 30 de marzo de 2022 a las 21:50:52 UTC+2, [email protected] > escribió: > >> Just did it again on me. Deleting the file again to fix it but would be >> great if I could fix it. Any advise? >> >> On Friday, March 18, 2022 at 11:17:56 AM UTC-6 [email protected] wrote: >> >>> The SSH Build Agents plugin make an sftp or scp (if one fail try the >>> other) with the user configured in the Jenkins Agent to copy a file in the >>> "Remote root directory" folder configured in the Agent config, nothing >>> special, if the user configured in the Agent can make scp/sftp to copy a >>> file in that folder it should not fail. >>> >>> The point where the Agent fails to copy the file is interesting, it >>> checks the value of the read bytes and fails if is <0 or >32768, I will >>> bet the value is `-1` and it is related to read the remoting.jar from the >>> Agent to check the md5, for some reason is returning an EOF >>> >>> >>> https://github.com/jenkinsci/trilead-ssh2/blob/master/src/com/trilead/ssh2/SFTPv3Client.java#L1231 >>> >>> https://github.com/jenkinsci/ssh-slaves-plugin/blob/main/src/main/java/hudson/plugins/sshslaves/SSHLauncher.java#L706 >>> El viernes, 18 de marzo de 2022 a las 16:10:56 UTC+1, [email protected] >>> escribió: >>> >>>> Hmmm, I deleted the remoting.jar file and was able to restart Jenkins >>>> and the node came up. Wonder if this is going to happen every we patch >>>> and >>>> boot this machine? >>>> >>>> On Friday, March 18, 2022 at 8:43:55 AM UTC-6 [email protected] wrote: >>>> >>>>> Hi! I have a node that is unable to launch. On the log it shows: >>>>> >>>>> [03/18/22 09:39:01] [SSH] Copying latest remoting.jar... >>>>> java.io.IOException: Could not copy remoting.jar into >>>>> '/home/myuser/checkout' 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:750) 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 >>>>> >>>>> I've set my perms on the checkout dir to 777, so it's not that it >>>>> doesn't have permission to write over the current remoting.jar that lives >>>>> there. Anyone have any clues or further trouble shooting advise? >>>>> Running Jenkins 2.232.1 on RHEL 7.9. >>>>> >>>>> Thanks - Eric >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/47eafb75-de8e-4b98-86fb-fffbf058fff0n%40googlegroups.com.
