Any help/suggestion on this? On Monday, November 26, 2018 at 11:24:45 AM UTC-5, [email protected] wrote: > > When I looked in Windows Server event logs, I see this error - > sigint to 81192 failed - killing as feedback > > I see this message multiple times and the number (81192) is defferent in > every error. > > On Monday, November 26, 2018 at 10:48:58 AM UTC-5, [email protected] > wrote: >> >> We have couple of more Windows Slaves, but we don't have any issue with >> those. Just this one slave going down often. >> >> On Monday, November 26, 2018 at 10:21:14 AM UTC-5, john.mellor wrote: >>> >>> 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, [email protected] 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/317ec954-f56e-4990-b183-55f1327aa9ae%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
