Mark Brookes wrote:
> Sorry to drag up an old thread. But do we have an eta for a new
> release of version 1.8 that contains the fix? I noticed that the 2.x
> versions have been updated, and wanted to make sure that 1.8 has not
> been left out by mistake.
I have just updated the backports for
Sorry to drag up an old thread. But do we have an eta for a new
release of version 1.8 that contains the fix? I noticed that the 2.x
versions have been updated, and wanted to make sure that 1.8 has not
been left out by mistake.
Thankyou
Mark
On Wed, 16 Dec 2020 at 10:03, Peter Statham
wrote:
On Wed, 16 Dec 2020 at 08:40, Christopher Faulet wrote:
>
> Le 11/12/2020 à 21:34, Peter Statham a écrit :
> >
> > The patch seems to fix the issue.
> >
>
> Peter,
>
> The fix was backported to the 1.8. Thanks !
>
> --
> Christopher Faulet
Hello Christopher,
Thank you for your time finding the
Le 11/12/2020 à 21:34, Peter Statham a écrit :
The patch seems to fix the issue.
Peter,
The fix was backported to the 1.8. Thanks !
--
Christopher Faulet
On Fri, 11 Dec 2020 at 15:21, Christopher Faulet wrote:
>
> Le 11/12/2020 à 11:45, Christopher Faulet a écrit :
> > Le 10/12/2020 à 19:38, Peter Statham a écrit :
> >> > Sorry for the delay in getting back to you. It is the same crash,
> >> > we've been trying to narrow down the exact
Le 11/12/2020 à 11:45, Christopher Faulet a écrit :
Le 10/12/2020 à 19:38, Peter Statham a écrit :
> Sorry for the delay in getting back to you. It is the same crash,
> we've been trying to narrow down the exact combination of compiler,
> libraries, kernel, hypervisor, etc. that causes
Le 10/12/2020 à 19:38, Peter Statham a écrit :
> Sorry for the delay in getting back to you. It is the same crash,
> we've been trying to narrow down the exact combination of compiler,
> libraries, kernel, hypervisor, etc. that causes the issue now that we
> know it isn't universal but
On Tue, 8 Dec 2020 at 14:55, Christopher Faulet wrote:
>
> Le 04/12/2020 à 21:24, Peter Statham a écrit :
> > I might have spoken too soon.
> >
> > The latest release of 1.8 works flawlessly on my debian desktop but
> > still crashes when I attempt the same configuration on a CentOS
> > virtual
Le 04/12/2020 à 21:24, Peter Statham a écrit :
I might have spoken too soon.
The latest release of 1.8 works flawlessly on my debian desktop but
still crashes when I attempt the same configuration on a CentOS
virtual machine on our VMWare cluster.
I'm not sure if this is down to differences in
On Mon, 26 Oct 2020 at 13:05, Peter Statham
wrote:
>
> On Mon, 19 Oct 2020 at 10:00, Christopher Faulet wrote:
> >
> > Le 16/10/2020 à 10:04, Christopher Faulet a écrit :
> > > Le 13/10/2020 à 14:53, Peter Statham a écrit :
> > >> Hello,
> > >>
> > >> We've found an issue when using agent checks
On Mon, 19 Oct 2020 at 10:00, Christopher Faulet wrote:
>
> Le 16/10/2020 à 10:04, Christopher Faulet a écrit :
> > Le 13/10/2020 à 14:53, Peter Statham a écrit :
> >> Hello,
> >>
> >> We've found an issue when using agent checks in conjunction with the
> >> weighted
> >> least connections
Le 16/10/2020 à 10:04, Christopher Faulet a écrit :
Le 13/10/2020 à 14:53, Peter Statham a écrit :
Hello,
We've found an issue when using agent checks in conjunction with the weighted
least connections algorithm in multithreaded mode. It seems to me as if it is
possible for next_eweight in
Le 13/10/2020 à 14:53, Peter Statham a écrit :
Hello,
We've found an issue when using agent checks in conjunction with the weighted
least connections algorithm in multithreaded mode. It seems to me as if it is
possible for next_eweight in struct server to be modified in another thread
Hello,
We've found an issue when using agent checks in conjunction with the
weighted least connections algorithm in multithreaded mode. It seems to me
as if it is possible for next_eweight in struct server to be modified in
another thread during the execution of fwlc_srv_reposition. If
14 matches
Mail list logo
