I am currently running Jenkins v1.609.3 on CentOS release 6.5 and have about 10 slaves connected to it.
The issue that I have is that when I attempt a reboot, the jenkins log hangs on ‘Attempting to connect to slave xyz’. After multiple reboot attempts, it finally makes it pass that ‘error’ and jenkins comes up. I have checked the slaves and I do see a slave.jar file on all of them. What is weird is that I don’t have ANY ‘<slave>’ section in the master jenkins config.xml file so where is Jenkins finding the slaves to connect to? Is there a way to tell jenkins to ignore connecting to a slave if it has an issue and ‘keep moving’ to bring up jenkins? Where in jenkins server are the slave configs defined? I don’t see them anywhere in the config.xml on MASTER. Could it be cached somewhere? Thanks, Ashish Yadav -- 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/D2BA9AA5.13658%25ashish.yadav%40firemon.com. For more options, visit https://groups.google.com/d/optout.
