Does it happen only on one agent? if you disconnect the Agent and connect
the agent again, Do you see the same issue?
checking the version you are using has about a year, the Jenkins Core you
have can use the latest version. Checking the changes in 1.32 there is a
change in the library used to
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
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
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 kuisat...@gmail.com wrote:
> The SSH Build Agents plugin make an sftp or scp (if one fail try the
> other) with the user configured in
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
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 eric@gmail.com wrote:
> Hi! I have a node that is unable to launch. On the
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
