It tries again and again, but the same error each time. And each times I am left with two new instances of java on the node still running and it piles up.
build 32256 0.1 0.3 5774136 50148 ? Sl 13:51 0:02 /usr/java/latest/bin/java -jar remoting.jar -workDir /home/build/jenkins build 32688 0.0 0.0 12912 1772 ? Ss 14:13 0:00 bash -c cd "/home/build/jenkins" && /usr/java/latest/bin/java -jar remoting.jar -workDir /home/build/jenkins torsdag 21. februar 2019 14.21.51 UTC+1 skrev Sverre Moe følgende: > > That was my fault. I forgot some lines and had paste it in from a > different try > > > [02/21/19 14:16:46] [SSH] Starting sftp client. [02/21/19 14:16:47] [SSH] > Copying latest remoting.jar... [02/21/19 14:16:47] [SSH] Copied 789,283 > bytes. Expanded the channel window size to 4MB [02/21/19 14:16:47] [SSH] > Starting agent process: cd "/home/build/jenkins" && /usr/java/latest/bin/java > -jar remoting.jar -workDir /home/build/jenkins Feb 21, 2019 2:16:48 PM > org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using > /home/build/jenkins/remoting as a remoting work directory Both error and > output logs will be printed to /home/build/jenkins/remoting ERROR: null > java.util.concurrent.CancellationException > at java.util.concurrent.FutureTask.report(FutureTask.java:121) > at java.util.concurrent.FutureTask.get(FutureTask.java:192) > at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:902) > at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) > at > jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) > at > jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > [02/21/19 14:20:16] Launch failed - cleaning up connection > Slave JVM has not reported exit code. Is it still running? > [02/21/19 14:20:16] [SSH] Connection closed. > > > > > > onsdag 20. februar 2019 20.14.39 UTC+1 skrev Ivan Fernandez Calvo følgende: >> >> Check the date time in both hosts, the log is not consistent there are >> more than an hour of clock difference > > -- 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/98d7a97f-f611-4c4c-8878-abd2ac2f544f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
