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
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:
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:
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
The host on vexxhost that were running out instance failed and we had to do
live migration to another host.
Regards,
--
Anton Baranov
Sr. System Operations Engineer
The Linux Foundation
On Tue Mar 12 06:48:32 2019, jgel...@cisco.com wrote:
> Hello,
>
> Could you, please, check Jenkins? All
Hi Dave,
I checked from different places and was able to ping6 gerrit.fd.io. Could you
provide traceroute6 to gerrit.fd.io and google.com?
Cheers,
--
Anton Baranov
Sr. System Operations Engineer
The Linux Foundation
On Thu Feb 21 10:26:54 2019, dbarach wrote:
> Folks,
>
> It looks like
k you Anton, Can you tell us the root cause after it's resolved.
> > > Trishan
> > >
> > >
> > > On Tue, Oct 17, 2017 at 11:56 AM, Anton Baranov via RT <
> > > fdio-helpd...@rt.linuxfoundation.org> wrote:
> > >
> > > >
>
:
> Thank you Anton, Can you tell us the root cause after it's resolved.
> Trishan
>
>
> On Tue, Oct 17, 2017 at 11:56 AM, Anton Baranov via RT <
> fdio-helpd...@rt.linuxfoundation.org> wrote:
>
> >
> > https://rt.linuxfoundation.org/Ticket/Display.html?id
We're working with our cloud provider to fix the issue.
On Tue Oct 17 10:39:05 2017, abaranov wrote:
> Thishan:
>
> I'm checking this right now
>
> Regards,
--
Anton Baranov
Systems and Network Administrator
The Linux Foundation
___
vpp-dev
Jan:
On my side I currently don't see any connectivity problems between jenkins and
VIRL servers. Please let me know if you're still having that issue. I'll keep
an eye on that problem and if it reapears I'll report that to our cloud
provider to check further.
Thanks,
--
Anton Baranov
2017, jgel...@cisco.com wrote:
> Hello Anton,
>
> Do you know, please, what was the root cause and how we can avoid such
> situation in the future?
>
> Thanks,
> Jan
>
> -Original Message-----
> From: Anton Baranov via RT [mailto:fdio-
> helpd...@rt.linuxfound
Hello,
We're checking that issue right now and will keep you updated
Thanks,
--
Anton Baranov
Systems and Network Administrator
The Linux Foundation
On Wed May 31 09:09:48 2017, hagbard wrote:
> -- Forwarded message --
> From: Jan Gelety -X (jgelety - PANTHEON
Hi Jan,
We've noticed network connectivity issues this weekend and early today. We're
working with our provider to fix the issues as soon as possible.
Thanks,
On Mon Nov 14 06:46:57 2016, jgel...@cisco.com wrote:
> Hello,
>
> We are experiencing occasional issues with access to
>
13 matches
Mail list logo
