Re: Latency spikes

Hello, I'm keep digging on this problem and that's what I've found so far: I have another one frontend/backend pair handled by the same instance, and it looks like whenever this backend goes slow, everything goes slow. Why one slow backend affects others? Any recommendations on how can I avoid

Can I specify a wildcard redirect

Hi all, one of my clients is looking for a wildcard redirect to get redirects from www.example.com/de/* to www.example.com/* I know how to do just the opposite, but for this one I couldn't find a solution in the documentation. Any chance that can be done? Thanks Jürgen

Re: Can I specify a wildcard redirect

Hello Jürgen Below is a link to the haproxy manual which will tell you exactly what you wish to know. https://www.haproxy.com/doc/aloha/7.0/haproxy/http_redirection.html and something like this will be what you are looking to do acl is_de path_beg -i /de acl is_domain hdr(host) -i

Re: HAProxy reloads lets old and outdated processes

Hello, Am 24.10.2016 um 22:32 schrieb Pavlos Parissis: IMHO: Ask the users to not perform reloads every 2miliseconds. It is insane. You may spend X hours on this which will make the code a bot more complex and cause possible breakages somewhere else. Not fixing *real world issues* because

Re: HAProxy reloads lets old and outdated processes

Hi guys, On Tue, Oct 25, 2016 at 12:42:26AM +0200, Lukas Tribus wrote: > Not fixing *real world issues* because we don't agree with the use-case or > there is a design misconception somewhere else is dangerous. We don't have > to support every single obscure use-case out there, that's not what I

RE: HAProxy reloads lets old and outdated processes

> Same for all of them. Very interesting, SIGUSR2 (12) is set > in SigIgn :-)  One question is "why", but at least we know we > have a workaround consisiting in unblocking these signals in > haproxy-systemd-wrapper, as we did in haproxy. > Care to retry with the attached patch ? Same behaviour.

Re: HAProxy reloads lets old and outdated processes

Hi Pierre, On Mon, Oct 24, 2016 at 12:16:32PM +, Pierre Cheynier wrote: > $ grep ^Sig /proc/43135/status > SigQ:    0/192473 > SigPnd:     > SigBlk:     > SigIgn:    1000 > SigCgt:    000180004803 (...) Same for all of them. Very interesting,

Re: HAProxy reloads lets old and outdated processes

On 24 October 2016 at 13:46, Pierre Cheynier wrote: > Hi, > > Sorry, wrong order in the answers. > > > Yes it has something to do with it because it's the systemd-wrapper which > > delivers the signal to the old processes in this mode, while in the > normal > > mode the

RE: HAProxy reloads lets old and outdated processes

Hi, Sorry, wrong order in the answers. > Yes it has something to do with it because it's the systemd-wrapper which > delivers the signal to the old processes in this mode, while in the normal > mode the processes get the signal directly from the new process. Another > important point is that

Re: HAProxy reloads lets old and outdated processes

On Mon, Oct 24, 2016 at 01:09:59PM +, Pierre Cheynier wrote: > > Same for all of them. Very interesting, SIGUSR2 (12) is set > > in SigIgn :-)  One question is "why", but at least we know we > > have a workaround consisiting in unblocking these signals in > > haproxy-systemd-wrapper, as we did

RE: HAProxy reloads lets old and outdated processes

> A solution I use is to delay next reload in systemd unit until a > reload is in progress. Unfortunately, even when doing this you can end up in the situation described before, because for systemd a reload is basically a SIGUSR2 to send. You do not wait for some callback saying "I'm now OK and

Re: HAProxy reloads lets old and outdated processes

Hi, here is the idea : [...] ExecReload= ExecReload=/bin/kill -USR2 $MAINPID [...] not the sexiest solution but it do the job and I never got the problem anymore ;) 2016-10-24 17:43 GMT+02:00 Pierre Cheynier : >> A solution I use is to delay next reload in systemd unit

Re: HAProxy reloads lets old and outdated processes

Hi, I had similar issues when reloading haproxy with lot of ssl (long to fork). A solution I use is to delay next reload in systemd unit until a reload is in progress. 2016-10-24 17:06 GMT+02:00 Willy Tarreau : > On Mon, Oct 24, 2016 at 01:09:59PM +, Pierre Cheynier wrote: >> >

RE: Issue with windows IE 11 and Edge

We have updated our test instance of HAProxy to 1.6.9 but are still able to reproduce the issue. From: Stroehmann, James Sent: Friday, October 07, 2016 2:44 PM To: haproxy@formilux.org Subject: Issue with windows IE 11 and Edge We have a website that is setup like this: CDN -> HAPROXY -> ELB

Re: SSL patches

Hi, thank you for the tests. It is exactly the last test. The patches seems to be good. The patches can be merged, if it is possible. @Emeric, all the tests that you asked are done and positive. Thanks, Thierry On Mon, 24 Oct 2016 16:08:57 +0200 Beluc wrote: > Hi, > >

Re: SSL patches

Hi Thierry, On Mon, Oct 24, 2016 at 06:32:29PM +0200, Thierry Fournier wrote: > Hi, thank you for the tests. It is exactly the last test. The patches > seems to be good. > > The patches can be merged, if it is possible. OK I've merged them now, thanks Thierry for doing this, and thanks Beluc

Re: HAProxy reloads lets old and outdated processes

Hi Pierre, On Mon, Oct 24, 2016 at 12:46:34PM +, Pierre Cheynier wrote: > Unfortunately, I remember we had the same issue (but less frequently) on > CentOS6 which is init-based. OK but be careful, we used to have other issues with signals in the past, it's not necessarily exactly the same

Re: HAProxy reloads lets old and outdated processes

Hi again, On Mon, Oct 24, 2016 at 07:41:06PM +0200, Willy Tarreau wrote: > I don't know if this is something you're interested in experimenting > with. This is achieved using fcntl(F_SETLKW). It should be done in the > wrapper as well. Finally I did it and it doesn't help at all. The

RE: HAProxy reloads lets old and outdated processes

Hi, > Pierre, could you please issue "grep ^Sig /proc/pid/status" for each > wrapper and haproxy process ? I'm interested in seeing SigIgn and > SigBlk particularly. > Sure, here is the output for the following pstree: $ ps fauxww | grep haproxy | grep -v grep root 43135  0.0  0.0  46340 

S FTP + HA PROXY confutation facing one serious issue.

Hello HaProxy Team, *MyObjective*:Client upload file via HaProxy and it will upload in sftp servers *example*: expected this type of configuration in Ha Proxy a.kk.com 192.168.0.1(sftp 1 server ip) b.kk.com 192.168.0.2(sftp

Re: Can I specify a wildcard redirect

Hi Andrew, Thanks for your quick reply and yes, I'm using the manual almost daily. But my question is not covered, I guess. Also your example is not working as it is always redirecting to the front page, but we would require wildcards. Examples: http://www.example.com/de/page-one =>

Re: Can I specify a wildcard redirect

Hello Jürgen In that case I think you will want something like acl de_url path_beg /de reqrep ^([^\ :]*)\ /de/\d+/(.+)/? \1\ /\2 redirect prefix / code 301 if de_url Regards Andrew Smalley Loadbalancer.org Ltd. On 24 October 2016 at 10:19, Jürgen Haas

Testers needed [Re: HAProxy reloads lets old and outdated processes]

On Mon, Oct 24, 2016 at 09:13:13PM +0200, Willy Tarreau wrote: > BTW, that just makes me realize that we also have another possibility for this > precisely using a pipe (which are more portable than mandatory locks). Let's > see if that would work. The wrapper creates a pipe then forks. The child

Re: HAProxy reloads lets old and outdated processes

On 24/10/2016 09:13 μμ, Willy Tarreau wrote: > Hi again, > > On Mon, Oct 24, 2016 at 07:41:06PM +0200, Willy Tarreau wrote: >> I don't know if this is something you're interested in experimenting >> with. This is achieved using fcntl(F_SETLKW). It should be done in the >> wrapper as well. > >