We have that problem all the time. IMHO the JNLP connectivity to the master is not robust enough to be used.
I have tried setting up the agent connection as a service per the Jenkins doc, but it still cannot survive momentary network or performance outages. The only way that I have managed to get this machine consistent, is to reboot the Windows machine and the service will shortly re-establish connectivity. JNLP connections are just-plain defective. On Mon, 2018-11-26 at 07:06 -0800, gotviser...@gmail.com wrote: Hello, We have a Windows Server 2016 Jenkins Slave. The Jenkins service in this slave goes down at times. We then go back and start it manually though the service is set to start automatically. Need help figuring out what's causing it to go down and why it isn't coming back online on its own. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0643151142ab642b3a0117ea0b42ab1e41ccfda3.camel%40esentire.com. For more options, visit https://groups.google.com/d/optout.
