Hi Christopher / Willy,
On Tue, Nov 28, 2017 at 10:28:20AM +0100, Christopher Faulet wrote:
Here is a patch that should fix the deadlock. Could you confirm it fixes
your bug ?
Fix confirmed.
Thanks,
PiBa-NL / Pieter
Hi Christopher,
On Tue, Nov 28, 2017 at 10:28:20AM +0100, Christopher Faulet wrote:
> Here is a patch that should fix the deadlock. Could you confirm it fixes
> your bug ?
At least it works for me, previously a config with a mailer would
immediately go to 100% CPU once reporting a down backend,
Le 28/11/2017 à 07:25, Willy Tarreau a écrit :
Hi Pieter,
On Mon, Nov 27, 2017 at 09:43:52PM +0100, PiBa-NL wrote:
Hi List,
I thought i 'reasonably' tested some of 1.8.0's options.
Today i put it into 'production' on my secondary cluster node and notice it
takes 100% cpu...
G.. bad.
Hi Pieter,
On Mon, Nov 27, 2017 at 09:43:52PM +0100, PiBa-NL wrote:
> Hi List,
>
> I thought i 'reasonably' tested some of 1.8.0's options.
> Today i put it into 'production' on my secondary cluster node and notice it
> takes 100% cpu...
G.. bad. This sounds like another case of recursive
Hi List,
I thought i 'reasonably' tested some of 1.8.0's options.
Today i put it into 'production' on my secondary cluster node and notice
it takes 100% cpu... I guess i should have tried such a thing last week.
My regular config with 10 frontends and total 13 servers seems to
startup fine
5 matches
Mail list logo