I increased idle timeout from 10min to 60min. Let's see if that makes any
difference.
Regards,
--
Anton Baranov
Sr. System Operations Engineer
The Linux Foundation
On Tue Apr 30 10:03:46 2019, vrpo...@cisco.com wrote:
> >> interleaved by quick periods of activity
>
> >>> 09:26:36 ++ sleep 19
Haproxy reload happened at that time: 2019-04-30 16:16:29. Could you give
another try ?
On Tue Apr 30 12:40:42 2019, vrpo...@cisco.com wrote:
> > I increased idle timeout from 10min to 60min.
>
> Was it around the time this [2] job failed recently?
>
> 16:14:44 ++ sleep 184s
> 16:16:29 FATAL: c
Hello Jan
>From logs I see that the job was waiting (sleep) from 04:45:12 til 05:26:36
>which could cause jnlp session to timed out as we have 10m idle timeout
>(client and server side) set on jenkins.fd.io
Could you check that error:
05:26:36 Reservation unsuccessful:
05:26:36 mkdir: cannot
Hello Vratko,
Thank you for explanation. I'm wondering within that period of time when
reservation was unsuccessful (~40min) does the job keep jnlp connection alive
(send any keepalive packages)?
I checked the haproxy node where jnlp is runnining and I don't see any DOWN
notification for it
