Re: [ANNOUNCE] haproxy-1.9.0

Am 20.12.2018 um 06:48 schrieb Willy Tarreau: > On Wed, Dec 19, 2018 at 11:31:33PM +0100, Aleksandar Lazic wrote: >>> Well, I know that so quick a summary doesn't do justice to the developers >>> having done all this amazing work, but I've seen that some of my coworkers >>> have started to write an

Re: Http HealthCheck Issue

Hi Praveen. Please keep the list in the loop, thanks. Am 20.12.2018 um 07:00 schrieb UPPALAPATI, PRAVEEN: > Hi Alek, > > Now I am totally confused: > > When I say : > > > backend bk_8093_read > balancesource > http-response set-header X-Server %s > option log-health-checks >

[PATCH 0/4] A few fixes for reg tests.

From: Frédéric Lécaille Hi ML, Here is a series of patches to fix a few reg testing issues. Fred. Frédéric Lécaille (4): REGTEST: Fix a typo about barrier type. REGTEST: Be less Linux specific with a syslog regex. REGTEST: Missing enclosing quotes for ${tmpdir} macro. REGTEST: Exclude f

[PATCH 1/4] REGTEST: Fix a typo about barrier type.

From: Frédéric Lécaille Fix a typo, furthermore there is no reason to use a barrier with "sock" as type which are more varnish cache specific: used to synchronize the VCL. --- reg-tests/checks/s0.vtc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reg-tests/checks/s0.

[PATCH 2/4] REGTEST: Be less Linux specific with a syslog regex.

From: Frédéric Lécaille This patch makes at least this test pass on FreeBSD systems. The regex to be matched with syslog message was too much Linux specific. --- reg-tests/checks/s3.vtc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reg-tests/checks/s3.vtc b/reg-test

[PATCH 4/4] REGTEST: Exclude freebsd target for some reg tests.

From: Frédéric Lécaille This patch excludes freebsd target for health-checks reg tests which rely on TCP_DEFER_ACCEPT usage. This is specific to Linux. --- reg-tests/checks/s0.vtc | 1 + reg-tests/checks/s1.vtc | 2 ++ reg-tests/checks/s2.vtc | 1 + 3 files changed, 4 insertions(+)

[PATCH 3/4] REGTEST: Missing enclosing quotes for ${tmpdir} macro.

From: Frédéric Lécaille --- reg-tests/connection/b0.vtc | 4 ++-- reg-tests/seamless-reload/b0.vtc | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/reg-tests/connection/b0.vtc b/reg-tests/connection/b0.vtc index 50bb7494..9b36c45a 100644 --- a/reg-tes

Re: [ANNOUNCE] haproxy-1.9.0

On Thu, Dec 20, 2018 at 09:17:00AM +0100, Aleksandar Lazic wrote: > Runtime API Improvements: It would be nice when you add a block that hanging > or > dead processes can also be debugged with this API now. Maybe I have overseen > it. It is already the case. It's not shown on the article, but th

DNS resolution issue with Docker swarm and HAProxy 1.8.15/1.9.0

Hello, We are running HAProxy in our Docker (18.09.0) swarm and we are relying on the Docker embedded DNS server for service discovery. The backend servers are configured to resolve the IP addresses via a "resolvers" config entry pointing to the Docker embedded DNS running on "127.0.0.11". Up to

Re: DNS resolution issue with Docker swarm and HAProxy 1.8.15/1.9.0

Hi, On Thu, Dec 20, 2018 at 03:42:40PM +0100, Leonhard Wimmer wrote: > Hello, > > We are running HAProxy in our Docker (18.09.0) swarm and we are relying on > the Docker embedded DNS server for service discovery. > > The backend servers are configured to resolve the IP addresses via a > "resolve

Re: DNS resolution issue with Docker swarm and HAProxy 1.8.15/1.9.0

Hi, On Thu, Dec 20, 2018 at 16:58, Jerome Magnin wrote: > this is indeed a regression in haproxy. thanks for reporting it. > attached patch should fix it. > CC'ing Remi as the original author, and Baptiste, as DNS maintainer. Thank you for the lightning-fast response! I can confirm that this pa

Re: DNS resolution issue with Docker swarm and HAProxy 1.8.15/1.9.0

On Thu, Dec 20, 2018 at 5:01 PM Jerome Magnin wrote: > Hi, > > On Thu, Dec 20, 2018 at 03:42:40PM +0100, Leonhard Wimmer wrote: > > Hello, > > > > We are running HAProxy in our Docker (18.09.0) swarm and we are relying > on > > the Docker embedded DNS server for service discovery. > > > > The bac

Re: DNS resolution issue with Docker swarm and HAProxy 1.8.15/1.9.0

On Thu, Dec 20, 2018 at 04:58:48PM +0100, Jerome Magnin wrote: > this is indeed a regression in haproxy. thanks for reporting it. > attached patch should fix it. > CC'ing Remi as the original author, and Baptiste, as DNS maintainer. Good catch, the patch looks obviously good, I've just merged it.

HA Proxy Load Balancer

We are testing the load balancer and it's working but I can't see how to direct the server to a specific website such as server.net/site. Is this possible? Syntax? Thanks! CYPRESS-FAIRBANKS ISD CONFIDENTIALITY NOTICE: This email, including any attachments, is for the sole use of the intended rec

Re: HA Proxy Load Balancer

Hi Lance. Am 20-12-2018 18:20, schrieb Lance Melancon: We are testing the load balancer and it's working but I can't see how to direct the server to a specific website such as server.net/site. Is this possible? Syntax? Thanks! Well yes. I think it is a good starting point to read and underst

Re: [ANNOUNCE] haproxy-1.9.0

Hi Willy. Am 20-12-2018 10:29, schrieb Willy Tarreau: On Thu, Dec 20, 2018 at 09:17:00AM +0100, Aleksandar Lazic wrote: Runtime API Improvements: It would be nice when you add a block that hanging or dead processes can also be debugged with this API now. Maybe I have overseen it. It is alrea

RE: HA Proxy Load Balancer

Thanks for the info. Unfortunately I am not a programmer by a long shot and syntax is a big problem for me. I tried a few things but no luck and I can't find any examples of a redirect. So do I need both the backend and acl statements? I'm simply trying to use mysite.net to direct to mysite.net/w

Re: DNS resolution issue with Docker swarm and HAProxy 1.8.15/1.9.0

❦ 20 décembre 2018 17:14 +01, Willy Tarreau : >> this is indeed a regression in haproxy. thanks for reporting it. >> attached patch should fix it. >> CC'ing Remi as the original author, and Baptiste, as DNS maintainer. > > Good catch, the patch looks obviously good, I've just merged it. > Thanks

Re: DNS resolution issue with Docker swarm and HAProxy 1.8.15/1.9.0

Hi, Am Do., 20. Dez. 2018 um 22:22 Uhr schrieb Vincent Bernat : > Is it important enough for an 1.8.16? Is it important enough for > distributors to release a fixed version? Why doesn't it affect most DNS > implementations? Please find attached a very short pcap with 4 packets: 2 DNS requests and

Re: DNS resolution issue with Docker swarm and HAProxy 1.8.15/1.9.0

Hi Vincent, On Thu, Dec 20, 2018 at 10:22:25PM +0100, Vincent Bernat wrote: > ❦ 20 décembre 2018 17:14 +01, Willy Tarreau : > > >> this is indeed a regression in haproxy. thanks for reporting it. > >> attached patch should fix it. > >> CC'ing Remi as the original author, and Baptiste, as DNS ma

Re: HA Proxy Load Balancer

Hi Lance. Am 20-12-2018 21:41, schrieb Lance Melancon: Thanks for the info. Unfortunately I am not a programmer by a long shot and syntax is a big problem for me. I tried a few things but no luck and I can't find any examples of a redirect. So do I need both the backend and acl statements? I'm s

Re: DNS resolution issue with Docker swarm and HAProxy 1.8.15/1.9.0

Hi guys, On Thu, Dec 20, 2018 at 10:53:21PM +0100, Jerome Magnin wrote: > Hi Vincent, > > On Thu, Dec 20, 2018 at 10:22:25PM +0100, Vincent Bernat wrote: > > ? 20 décembre 2018 17:14 +01, Willy Tarreau : > > > > >> this is indeed a regression in haproxy. thanks for reporting it. > > >> attache

BUG/MAJOR: dns: overflowed dns name start position causing invalid dns error

Dear Haproxy Maintainers, In dns_read_name() when dns name is used with name compression and start position of name is greater than 255, name is read from incorrect position ( actual position%256). This causes "Invalid dns error" and backend is marked as down permanently. eg: hexadecimal value at