I'd check the java processes to see what they are doing (e.g. are they stuck on network connections or something) - I've had issues like that when the jenkins windows service exe used to be (still is?) signed by a cert that .Net was trying to go out to the internet to confirm authenticity.
Richard. On Tue, Sep 18, 2012 at 2:52 AM, phil swenson <phil.swen...@gmail.com> wrote: > We have troubles with Jenkins Slaves stopping working and having to manually > restart the windows service on every node (15 nodes). > > Last week, windows update ran and all the servers got restarted. The > Jenkins Slave service only started on 5 of the 15. I had to ssh into each > and start the service. > > Today all nodes are marked offline. > > The services were not running, I suspect every machine was bounced by > windows update. > > > It appears that the jenkins service startup is flakey. Even when I run it > manually I get stuff like this: > > Administrator@DAEAP86187 ~ > $ net start "Jenkins Slave" > The service is not responding to the control function. > > More help is available by typing NET HELPMSG 2186. > > > Administrator@DAEAP86187 ~ > $ net start "Jenkins Slave" > The Jenkins Slave service is starting. > The Jenkins Slave service was started successfully. > > > Ideas? Suggestions?
