Hi Pieter,
On Mon, Apr 16, 2018 at 02:22:48AM +0200, PiBa-NL wrote:
> EVFILT_READ, EV_ADD (8)
> EVFILT_WRITE, EV_DELETE (8)
> EVFILT_READ, EV_ADD (7)
> Events changed:3 result:-1 err:2 <<< ERROR while deleting a non
> existing event
>
> After this the KernelEvent for FD 7
Hi Willy,
Op 15-4-2018 om 23:08 schreef Willy Tarreau:
Well to be clear, I'm pretty sure we're hiding the dust under the carpet
here, even if it fixes the problem in your case. What I need to do is to
actually understand why we end up in this situation.
Okay added a little more code/error
Hi
On 12/04/2018 19:16, Ayush Goyal wrote:
> Hi,
>
> I have a question regarding haproxy backend connection behaviour. We
> have following setup:
>
> +-+ +---+
> | haproxy |>| nginx |
> +-+ +---+
>
> We use a haproxy cluster for ssl off-loading and then
Hi Pieter,
On Sun, Apr 15, 2018 at 10:55:34PM +0200, PiBa-NL wrote:
> Hi Willy,
>
> Sending a patch proposal after like 40 hours of looking through what happens
> and what event we might be missing, im now changing +-40 lines of code.. And
> actually not 'really' changing the events requested..
Hi Willy,
Sending a patch proposal after like 40 hours of looking through what
happens and what event we might be missing, im now changing +-40 lines
of code.. And actually not 'really' changing the events requested.. But
rather kinda bringing the old 'previous state' comparison back..
I'm working on making my application capable of handling service
restarts on the back end with zero loss or interruption. It runs on two
servers behind haproxy.
At application shutdown, I'm setting a flag that makes the healthcheck
fail, and then keeping the application running for thirty
Kernel info:
root@lb1:/etc/haproxy# uname -a
Linux lb1 3.13.0-52-generic #86-Ubuntu SMP Mon May 4 04:32:59 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
Here's the haproxy version output:
root@lb1:/etc/haproxy# haproxy -vv
HA-Proxy version 1.5.12 2015/05/02
Copyright 2000-2015 Willy Tarreau
Hello,
Here is a small patch to fix a potential crash when using
CLI_ST_PRINT_FREE in an error path in the 'map' code.
The problematic part is in the 'add' feature but all other usages have
ben modified the same way to be consistent.
It also adds a missing error message in the SSL code when the
8 matches
Mail list logo