Re: Backup server takes too long to go active

On 4/25/2018 1:29 AM, Lukas Tribus wrote: You seem to be able to reproduce this easily, so please share the logs when this happens including the requests (don't use dontlognull), so that we can see the server up/down events and the all the successful and failing requests together with

Re: Backup server takes too long to go active

Hello Shawn, On 25 April 2018 at 03:55, Shawn Heisey wrote: > I'm hoping to figure out how to make a backup server transition immediately > to active as soon as the primary server is marked down. If you need > additional info, please let me know. Like I said in the other

Re: Backup server takes too long to go active

On Tue, Apr 24, 2018 at 07:55:43PM -0600, Shawn Heisey wrote: > I'm hoping to figure out how to make a backup server transition immediately > to active as soon as the primary server is marked down.  If you need > additional info, please let me know. I'm a bit worried because this has been the

Re: Backup server takes too long to go active

On 4/24/2018 3:38 PM, Cyril Bonté wrote: Le 24/04/2018 à 23:07, Shawn Heisey a écrit : The configuration I had is with a backend that has two servers, one of them tagged as backup. This is the actual config that I had active when I saw the problem: backend be-cdn-9000 description Back

Re: Backup server takes too long to go active

Le 24/04/2018 à 23:07, Shawn Heisey a écrit : I sent this query to the list previously nine days ago. I got no response. Trying again. Next time reply to the thread you created, it's better to track which ones had responses. == Kernel info: root@lb1:/etc/haproxy# uname -a Linux

Backup server takes too long to go active

I sent this query to the list previously nine days ago. I got no response. Trying again. == 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: