Re: HAProxy Page Element Request Times Slowly Increase

Hi Caleb Anthony. Caleb Anthony have written on Wed, 17 May 2017 15:42:44 -0600: > Hello, > > Compression is enabled on a few backends, but not on the backend that > traffic is going to for these requests. However, IIS is configured to > compress the traffic. > > HA-Proxy version 1.6.11 2016/12

Re: 1.7.5 503 Timeouts with SNI backend

My final solution looked like: backend clientsite_ember default-server inter 10s resolve-prefer ipv4 server cf foobar.cloudfront.net:443 ssl verify required verifyhost foobar.cloudfront.net sni str(foobar.cloudfront.net) ca-file /etc/ssl/certs/ca-certificates.crt check port 80 resolvers dns (

Re: haproxy "inter" and "timeout check", retries and "fall"

> On May 18, 2017, at May 18, 2:58 AM, Jiafan Zhou > wrote: > > Hi Bryan, > > For reference: > > >> defaults >> timeout http-request10s >> timeout queue 1m >> timeout connect 10s >> timeout client 1m >> timeout server 1m >> time

Re: OpenSSL engine and async support

Hi Willy Tarreau. Willy Tarreau have written on Wed, 17 May 2017 22:10:58 +0200: > Hi Emeric, > > On Wed, May 17, 2017 at 09:49:32PM +0200, Emeric Brun wrote: > > More fixes, it appears stable now, even if session are closed > > during handshake. > > > > I also added the support of multiple asy

Re: haproxy doesn't restart after segfault on systemd

Hi again, On Fri, May 19, 2017 at 11:45:18AM +0200, William Lallemand wrote: > Hi, > > On Thu, May 18, 2017 at 05:25:26PM -0400, Patrick Hemmer wrote: > > So we had an incident today where haproxy segfaulted and our site went > > down. Unfortunately we did not capture a core, and the segfault mes

HAProxy 1.7.5: conn_cur value problem with peer stick-table

Hello all, I have problem to setup rate limiting with "conn_cur" information and stick-table shared using peers. The counter always increase without decrementing until key has expired. Following my configuration and my tests: I have 2 haproxy servers, a peers definition containing 2 servers and a

Re: haproxy doesn't restart after segfault on systemd

Hi, On Thu, May 18, 2017 at 05:25:26PM -0400, Patrick Hemmer wrote: > So we had an incident today where haproxy segfaulted and our site went > down. Unfortunately we did not capture a core, and the segfault message > logged to dmesg just showed it inside libc. So there's likely not much > we can d

Re: HAProxy 1.6.3: 100% cpu utilization for >17 days with 1 connection

❦ 19 mai 2017 08:28 +0200, Willy Tarreau  : > The problem is that it's what was being attempted during the days of 1.3, > resulting in still highly bogus versions being deployed in field and > users being very confident in them because they were recently updated. > These days, every patch going i