On Thu, Jun 11, 2015 at 07:26:00AM +0000, Emmanuel Dreyfus wrote: > In my opinion the fix to this problem is to start new VM. I was busy > on other fronts hence I did not watched the situation, but it is still > grim, with most NetBSD slaves been in screwed state. We need to spin > more. Launching the slave on the new VM fails, but for once we have a maningful error: either DNS names are duplicated, or jenkins has a bug. <===[JENKINS REMOTING CAPACITY]===>ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. java.lang.IllegalStateException: Already connected at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:466) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:371) at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:945) at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:133) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:711) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) [06/11/15 02:37:46] Launch failed - cleaning up connection [06/11/15 02:37:46] [SSH] Connection closed. -- Emmanuel Dreyfus manu@xxxxxxxxxx _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
