On Thu, Jan 25, 2018 at 11:28:38AM +0100, Christopher Faulet wrote:
> Thanks for tests guys. Willy, you can merge the patch.
Applied, thanks!
Willy
Le 24/01/2018 à 23:54, Paul Lockaby a écrit :
This patch works for me. Thank you!
On Jan 24, 2018, at 1:02 PM, Christopher Faulet wrote:
Le 24/01/2018 à 17:21, Paul Lockaby a écrit :
Sorry, I know this list is super busy and that there are a number of other more
This patch works for me. Thank you!
> On Jan 24, 2018, at 1:02 PM, Christopher Faulet wrote:
>
> Le 24/01/2018 à 17:21, Paul Lockaby a écrit :
>> Sorry, I know this list is super busy and that there are a number of other
>> more important issues that need to be worked
Hi Christopher,
Patch seems to work for me.
Maybe Paul can confirm as well.
Regards,
PiBa-NL / Pieter
Op 24-1-2018 om 22:02 schreef Christopher Faulet:
Le 24/01/2018 à 17:21, Paul Lockaby a écrit :
Sorry, I know this list is super busy and that there are a number of
other more important
Hi Paul, List,
Op 24-1-2018 om 17:21 schreef Paul Lockaby:
Sorry, I know this list is super busy and that there are a number of other more
important issues that need to be worked through but I'm hoping one of the
maintainers has been able to confirm this bug?
I can reproduce it indeed with
Le 24/01/2018 à 17:21, Paul Lockaby a écrit :
Sorry, I know this list is super busy and that there are a number of other more
important issues that need to be worked through but I'm hoping one of the
maintainers has been able to confirm this bug?
Hi,
Sorry Paul. As you said, we are pretty
Sorry, I know this list is super busy and that there are a number of other more
important issues that need to be worked through but I'm hoping one of the
maintainers has been able to confirm this bug?
Thanks,
-Paul
> On Jan 17, 2018, at 10:27 AM, Paul Lockaby wrote:
>
> Ok
Ok I've tracked this problem down specifically to the usage of check tracking.
That is to say, the backend "example-api" is set to track the backend
"example-http". When that tracking is enabled and one of the servers in the
backend goes down then all of haproxy goes down and never recovers.
I'm experiencing a problem that I can't diagnose but I can recreate pretty
consistently. I have a single server that responds for example.com and
api.example.com and it runs haproxy. All the names run through an SSL front
door but an ACL makes it such that requests for example.com get sent to
9 matches
Mail list logo