Re: Version 1.5.12, getting 502 when server check fails, but server is still working

On 4/17/2018 2:54 PM, Lukas Tribus wrote: >> Originally, the "hollywood" entry on the be-cdn-9000 backend (which you can >> see at the config I linked above) had the backup keyword. But what I >> noticed happening was that when planet went down, it took about ten >> additional seconds (no precise

Re: Version 1.5.12, getting 502 when server check fails, but server is still working

Hello Shawn, On 17 April 2018 at 15:24, Shawn Heisey wrote: >>> I described that issue in a separate message to the >>> list. I do have a workaround to that issue -- I'm no longer using >>> "backup" on any server entries for this service. >> >> Then I don't see how it

Re: Version 1.5.12, getting 502 when server check fails, but server is still working

On 4/17/2018 3:41 AM, Willy Tarreau wrote: Here I'm afraid we're all wasting a lot of time trying to guess what you have in your config that causes the problem. It's OK if you cannot post your config here, but please at least post a smaller one reproducing the issue so that we can help you. I

Re: Version 1.5.12, getting 502 when server check fails, but server is still working

On Mon, Apr 16, 2018 at 04:13:28PM -0600, Shawn Heisey wrote: > [ALERT] 105/095234 (7186) : config : backend 'be-cdn-9000', server > 'planet': unable to use chk-cdn-9000/planet fortracking: disable-on-404 > option inconsistency. > [ALERT] 105/095234 (7186) : config : backend 'be-cdn-9000', server

Re: Version 1.5.12, getting 502 when server check fails, but server is still working

On 4/16/2018 1:46 PM, Willy Tarreau wrote: > On Mon, Apr 16, 2018 at 10:03:44AM -0600, Shawn Heisey wrote: >> I am curious about why I couldn't use "track". > "track" means that your current server will always be in the same state > as the designated one. It will never run its own checks, and will

Re: Version 1.5.12, getting 502 when server check fails, but server is still working

On Mon, Apr 16, 2018 at 10:03:44AM -0600, Shawn Heisey wrote: > I am curious about why I couldn't use "track". "track" means that your current server will always be in the same state as the designated one. It will never run its own checks, and will receive notifications from the other one's state

Re: Version 1.5.12, getting 502 when server check fails, but server is still working

On 4/16/2018 6:43 AM, Jarno Huuskonen wrote: There's also http-check disable-on-404 (http://cbonte.github.io/haproxy-dconv/1.5/configuration.html#4.2-http-check%20disable-on-404) I couldn't get this to work at first.  If I put the disable-on-404 option in the actual back end, it complains

Re: Version 1.5.12, getting 502 when server check fails, but server is still working

Hello Shawn, On 16 April 2018 at 17:39, Shawn Heisey wrote: > I enabled the admin socket so that I could renew OCSP stapling. As far as I > understand, it can only be used on the load balancer machine itself, and I > think this is the only way to renew stapling other than

Re: Version 1.5.12, getting 502 when server check fails, but server is still working

On 4/16/2018 9:15 AM, Lukas Tribus wrote: Hello Shawn, please keep the mailing-list in the loop. Sorry about that.  Looks like the haproxy list doesn't set a reply-to header sending replies to the list.  Most mailing lists I have dealt with do this, so just hitting "reply" does the right

Re: Version 1.5.12, getting 502 when server check fails, but server is still working

On 4/16/2018 6:43 AM, Jarno Huuskonen wrote: There's also http-check disable-on-404 (http://cbonte.github.io/haproxy-dconv/1.5/configuration.html#4.2-http-check%20disable-on-404) So maybe first set flag that returns 404 on health check and only after thirty seconds fail the health check. This

Re: Version 1.5.12, getting 502 when server check fails, but server is still working

Hello Shawn, please keep the mailing-list in the loop. On 16 April 2018 at 16:53, Shawn Heisey wrote: >> Having said that, you'd be better off setting the server to >> maintenance mode instead of letting the health check fail (via >> webinterface or stats socket): >>

Re: Version 1.5.12, getting 502 when server check fails, but server is still working

Hi, On Mon, Apr 16, Lukas Tribus wrote: > On 15 April 2018 at 21:53, Shawn Heisey wrote: > > 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

Re: Version 1.5.12, getting 502 when server check fails, but server is still working

Hello, On 15 April 2018 at 21:53, Shawn Heisey wrote: > 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

Re: Version 1.5.12, getting 502 when server check fails, but server is still working

On Sun, 15 Apr 2018 at 20:56, Shawn Heisey wrote: > Would I need to upgrade beyond 1.5 to get that working? I don't have any info about your precise problem, but here's a quote from Willy's 1.9 thread within the last couple of months: "Oh, before I forget, since nobody