Re: problem in 1.8 with hosts going out of service

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 through but I'm hoping on

Re: problem in 1.8 with hosts going out of service

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 issue

Re: [PATCH] CONTRIB: log: emit warning when -sf/-sd cannot parse argument

Ping; this is a safe change to wanr about a confusing source of error when you don't quote the arguments to haproxy in a "soft reloading new config a lot" type of environment. On Thu, Dec 7, 2017 at 1:17 PM Chris Lane wrote: > > Previously, -sf and -sd command line parsing used atol which cannot

Re: problem in 1.8 with hosts going out of service (alive.txt+404+track)

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 you

Re: problem in 1.8 with hosts going out of service

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 b

Re: [PATCH] Fix build when compiling without threads traffic

On Wed, Jan 24, 2018 at 03:44:25PM +0100, Olivier Houchard wrote: > Hi, > > Commit 1605c7ae6154d8c2cfcf3b325872b1a7266c5bc2 broke building haproxy > without threads support. The attached patch should fix it. Oh, thank you Olivier. I didn't know that HA_SPINLOCK_T wasn't declared without threads,

h2 sending RSTs in response to RSTs

Hi, I patched Chromium to close the stream immediately after seeing END_STREAM. In testing, Chromium sends an RST (CANCEL) for this, but HAProxy replies with an RST (STREAM_CLOSED). This is a MUST NOT (though only a nuisance for me as Chromium will print warnings for it.): > To avoid looping, an

Re: mworker: seamless reloads broken since 1.8.1

Hi Pierre, On Wed, Jan 24, 2018 at 03:07:54PM +0100, Pierre Cheynier wrote: > Willy, I confirm that it works well again running the following version: > > $ haproxy -v > HA-Proxy version 1.8.3-945f4cf 2018/01/23 > > Added nbthread again, reloads are transparents. Excellent, many thanks for conf

Re: problem in 1.8 with hosts going out of service

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 I've tracked this p

How can I map bindings to the correct backend?

I have the following configuration: frontend default-tcp bind 192.168.52.12:5044 bind 192.168.52.12: bind 192.168.52.12:5556 bind 192.168.52.12:5672 bind 192.168.52.13:5672 mode tcp option tcplog use_backend %[dst_port,map(/etc/haproxy/tcp-bindings-to-backends.map,default)]

Re: tune.h2.initial-window-size not applied to connection windows

On Tue, Jan 23, 2018 at 2:13 PM, klzgrad wrote: > This tuning knob is probably only useful if it's also applied to the > overall connection windows in addition to stream windows. This should be fairly easy to do: --- a/src/mux_h2.c 2017-12-31 01:13:19.0 +0800 +++ b/src/mux_h2.c 20

[PATCH] Fix build when compiling without threads traffic

Hi, Commit 1605c7ae6154d8c2cfcf3b325872b1a7266c5bc2 broke building haproxy without threads support. The attached patch should fix it. Regards, Olivier >From 17e4494874b4a75da039f06f00f668d413038283 Mon Sep 17 00:00:00 2001 From: Olivier Houchard Date: Wed, 24 Jan 2018 15:41:04 +0100 Subject: [P

Re: mworker: seamless reloads broken since 1.8.1

On 23/01/2018 19:29, Willy Tarreau wrote: > Pierre, please give a try to the latest 1.8 branch or the next nightly > snapshot tomorrow morning. It addresses the aforementionned issue, and > I hope it's the same you're facing. > > Cheers, > Willy Willy, I confirm that it works well again running the

rate-limit sessions not consistent between ssl and non ssl traffic

Hi, I've been toying with haproxy and rate limiting lately, and noticed an odd behavior with rate-limit sessions, or maybe I misunderstood how it is supposed to be used. I'm using the following config: global maxconn 2 log 127.0.0.1 local0 userhaproxy chro

Re: h2 DATA padding ignored in flow control

Hi, On Wed, Jan 24, 2018 at 12:13:07PM +0800, klzgrad wrote: > Hi, > > I think I found a new issue while inspecting the source code. > > In h2_frt_transfer_data(), the paddings are not added to the > connection and stream flow control counters, h2c->rcvd_c and > h2c->rcvd_s. But it should, per R

Different health-check URI per server : how would you do that ?

Hi, We have a use-case in which the health-check URI is depending on the server-name (be reassured, only the health-check :) ). It would be something like: backend be_testmode http[...] option httpchk get /check HTTP/1.1\r\nHost: test.tld default-server inter 3s fall 3 rise 2   server srv01 10.2