Hi, It looks like increasing the ELB Timeout helped us! Thanks a lot!
On Wednesday, 3 June 2020 01:13:37 UTC-4, D'raj wrote: > > try increasing aws elb Idle timeout, by default its 60 sec > > > On Saturday, 30 May 2020 03:22:47 UTC+5:30, Vinod Krishna wrote: >> >> Hi, >> >> >> We have around 10 Jenkins Agents, each running on its own Windows 2016 >> EC2 instance. Java_slave is running as a service. The Jenkins master runs >> on a separate Amazon Linux instance. We are able to establish connectivity >> between the Master and Agents and jobs are running fine. >> >> However, for some reason, the Service goes offline at different intervals >> and comes back online. This is a repeated behavior and we are not able to >> find many logs from the Windows Event Viewer , except that it Says "Jenkins >> Slave stopping" . and the service comes back online. We installed NewRelic >> APM Agent to the server to check the Java metrics and there is minimal Heap >> consumption. The Java versions of both the Agent and Server are the same ( >> jdk1.8.0_211). We are not able to find the root cause of the Service being >> stopped abruptly and Jobs running on them gets killed. >> >> >> “"windows agent was marked offline: Connection was broken: >> java.nio.channels.ClosedChannelException"” >> >> >> Thanks in advance. >> >> Vinod >> > -- 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/cdd8e861-e2d5-41b9-8d4e-87f8be076467o%40googlegroups.com.
