question about -p and -sf/-st

Hello, I have a script which is reloading haproxy by running: haproxy -p /var/run/haproxy.pid -sf $(cat /var/run/haproxy.pid) [...] and noticed that occasionnally the pidfile was empty, leading to the old process not getting killed. I'm struggling to understand *why* the pidfile is

Re: [BUG] 100% cpu on each threads

On Mon, Jan 22, 2018 at 06:16:12PM +0100, Willy Tarreau wrote: > On Mon, Jan 22, 2018 at 05:47:55PM +0100, Willy Tarreau wrote: > > > strace: Process 12166 attached > > > [pid 12166] set_robust_list(0x7ff9bc9aa9e0, 24 > > > [pid 12166] <... set_robust_list resumed> ) = 0 > > > [pid 12166]

Re: [BUG] 100% cpu on each threads

Hello, Thanks for your answer Willy ! On Mon, Jan 22, 2018 at 05:47:55PM +0100, Willy Tarreau wrote: > Hi Marc, > > On Mon, Jan 22, 2018 at 03:18:20PM +0100, Marc Fournier wrote: > > Cyril Bonté <cyril.bo...@free.fr> writes: > > > > Hello, > > > &

Re: [BUG] 100% cpu on each threads

Cyril Bonté writes: Hello, > Im' not sure you saw Samuel Reed's mail. > He reported a similar issue some hours ago (High load average under > 1.8 with multiple draining processes). It would be interesting to find > a common configuration to reproduce the issue, so I add him

Re: feature request

Vladimír Houba ml. writes: Hello, > we have many backends with few permanent connections/each and I was > wondering if it is possible to send an email alert when no connection is > active on the backend. It is not possible to implement this feature on the > application

Re: 1.8.3 dns resolver ipv4/ipv6 undesirable behaviour

Marc Fournier <marc.fourn...@camptocamp.com> writes: > Simply adding "resolve-prefer ipv4" makes the symptom go away, so no big > deal. But I wanted to point this out, as it might bite others, and I'm > pretty sure 1.7.x didn't have this issue. It turns out that "re

1.8.3 dns resolver ipv4/ipv6 undesirable behaviour

Hello, Using the following (simplified) configuration, all the servers go (and stay) into maintenance mode about 30s after start up or config reload. Default "resolvers/hold timeout" I guess. These log lines get emitted: 2018-01-08T15:38:10.209195+00:00: Proxy dockercloud_hello-world started.

Re: http/2 - missing something ...

tried, just in case, to build / run the 1.7.x dev branch … neither seems to work ... > On Dec 16, 2015, at 12:10, Marc Fournier <scra...@hub.org> wrote: > > > Okay … thanks to Vincent/Lukas, I have a 1.6.2 built that has OpenSSL 1.0.2 > statically linked … so this line

http/2 - missing something ...

Okay … thanks to Vincent/Lukas, I have a 1.6.2 built that has OpenSSL 1.0.2 statically linked … so this line now works, in so far as letting the server start up: bind :443 ssl crt /etc/ssl/cert.pem no-sslv3 ciphers TLSv1.2 alpn h2,http/1.1 When I hit the server, the haproxy.log file

Re: http/2 - missing something ...

Damn … Apache does, but, Wordpress doesn’t … unless we’ve missed something, but you have to make a choice with Wordpress … either its a https:// site, or its a http:// site … they hard code the protocol / url right into the database … Any ETA on ALPN on the backend? 1.7? Or not until 1.8?

http/2 options

I’m working on a Debian Jessie (8) system, and need to get a verison of haproxy working that supports http/2 … I found this HOWTO for HAProxy+Jetty ( https://www.eclipse.org/jetty/documentation/current/http2-configuring-haproxy.html ), but when I do a ‘apt-get install haproxy’, it is

haproxy behind a proxy (incapsula)

Morning all … I’ve been fighting with an issue here, and have run out of ideas … We have a wordpress site, two webheads behind haproxy … balance leastconn … in front of haproxy, we are using Incapsula, as CDN/DDoS shield … if I am only running one webhead, everythign works great,

Re: haproxy behind a proxy (incapsula)

found it just after I sent this: balance hdr(X-Forwarded-For) testing right now, but *looks* like it fixes the issue … *cross fingers* On Jan 16, 2015, at 9:21 AM, Marc Fournier scra...@hub.org wrote: Morning all … I’ve been fighting with an issue here, and have run out of ideas

Re: redirecting based on Accept-Language

RTL languages. acl rtl req.fhdr(accept-language),language (de;es;fr;en;ar) ar use_backend rtl if rtl default_backend ltr Can you test this feature ? Thierry On Thu, 10 Apr 2014 11:00:38 +0200 Willy Tarreau w...@1wt.eu wrote: On Wed, Apr 09, 2014 at 01:50:28PM -0700, Marc

Re: redirecting based on Accept-Language

On Apr 9, 2014, at 05:05 , Thierry FOURNIER tfourn...@exceliance.fr wrote: On Tue, 8 Apr 2014 11:02:42 -0700 Marc Fournier scra...@hub.org wrote: as per the subject, has anyone done something like this? we’re setting up two backend pools, one geared to RTL languages, one to LTR … I’d

redirecting based on Accept-Language

as per the subject, has anyone done something like this? we’re setting up two backend pools, one geared to RTL languages, one to LTR … I’d like to set it up so that its transparent to the end user, so that if they come in requesting, for instance, Arabic, they get directed to the RTL pool,