Re: Traffic delivered to disabled server when cookie persistence is enabled after upgrading to 1.8.1

2017-12-21 Thread Willy Tarreau
On Fri, Dec 22, 2017 at 12:34:45AM +0100, Cyril Bonté wrote: > And after performing the same tests with the patch applied, I can confirm I > don't reproduce the issue anymore ;-) Cool, thanks for your feedback Cyril! Willy

Re: Traffic delivered to disabled server when cookie persistence is enabled after upgrading to 1.8.1

2017-12-21 Thread Cyril Bonté
Hi all, Le 21/12/2017 à 15:25, Willy Tarreau a écrit : On Thu, Dec 21, 2017 at 02:53:07PM +0100, Emeric Brun wrote: Hi All, This bug should be fixed using this patch (patch on dev, abd should be backported in 1.8). now applied to both branches,, thanks! Willy And after performing the

Re: Traffic delivered to disabled server when cookie persistence is enabled after upgrading to 1.8.1

2017-12-21 Thread Willy Tarreau
On Thu, Dec 21, 2017 at 02:53:07PM +0100, Emeric Brun wrote: > Hi All, > > This bug should be fixed using this patch (patch on dev, abd should be > backported in 1.8). now applied to both branches,, thanks! Willy

Re: Traffic delivered to disabled server when cookie persistence is enabled after upgrading to 1.8.1

2017-12-21 Thread Emeric Brun
Hi All, This bug should be fixed using this patch (patch on dev, abd should be backported in 1.8). R, Emeric On 12/21/2017 10:42 AM, Greg Nolle wrote: > Thanks guys! I should be able to test the new version this weekend if you are > able to issue it before then. > > Best regards, > Greg > >

Re: Traffic delivered to disabled server when cookie persistence is enabled after upgrading to 1.8.1

2017-12-21 Thread Greg Nolle
Thanks guys! I should be able to test the new version this weekend if you are able to issue it before then. Best regards, Greg On Thu, Dec 21, 2017 at 12:15 AM, Willy Tarreau wrote: > On Thu, Dec 21, 2017 at 12:04:11AM +0100, Cyril Bonté wrote: > > Hi Greg, > > > > Le 20/12/2017 à

Re: Traffic delivered to disabled server when cookie persistence is enabled after upgrading to 1.8.1

2017-12-20 Thread Willy Tarreau
On Thu, Dec 21, 2017 at 12:04:11AM +0100, Cyril Bonté wrote: > Hi Greg, > > Le 20/12/2017 à 22:42, Greg Nolle a écrit : > > Hi Andrew, > > > > Thanks for the info but I'm afraid I'm not seeing anything here that > > would affect the issue I'm seeing, and by the way the docs don't > > indicate

Re: Traffic delivered to disabled server when cookie persistence is enabled after upgrading to 1.8.1

2017-12-20 Thread Cyril Bonté
Hi Greg, Le 20/12/2017 à 22:42, Greg Nolle a écrit : Hi Andrew, Thanks for the info but I’m afraid I’m not seeing anything here that would affect the issue I’m seeing, and by the way the docs don’t indicate that the cookie names have to match the server names. First, don't worry about the

Re: Traffic delivered to disabled server when cookie persistence is enabled after upgrading to 1.8.1

2017-12-20 Thread Greg Nolle
Hi Andrew, Thanks for the info but I’m afraid I’m not seeing anything here that would affect the issue I’m seeing, and by the way the docs don’t indicate that the cookie names have to match the server names. That being said, I tried using your settings and am still seeing the issue (see below

Re: Traffic delivered to disabled server when cookie persistence is enabled after upgrading to 1.8.1

2017-12-20 Thread Andrew Smalley
Also our cookie line looks as below  cookie SERVERID maxidle 30m maxlife 12h insert nocache indirect Andruw Smalley Loadbalancer.org Ltd. www.loadbalancer.org +1 888 867 9504 / +44 (0)330 380 1064 asmal...@loadbalancer.org Leave a Review | Deployment Guides | Blog On 20 December 2017 at

Re: Traffic delivered to disabled server when cookie persistence is enabled after upgrading to 1.8.1

2017-12-20 Thread Andrew Smalley
Greg its just been pointed out your cookies are wrong, they would usually match your server name. I would change this server server-1-google www.google.com:80 check cookie google server server-2-yahoo www.yahoo.com:80 check cookie yahoo to this server server-1-google www.google.com:80

Re: Traffic delivered to disabled server when cookie persistence is enabled after upgrading to 1.8.1

2017-12-20 Thread Andrew Smalley
Hi Greg Apologies I was confused with the terminology we use here, Indeed MAINT should be the same as our HALT feature, Maybe you can share your config and we can see what's wrong? Andruw Smalley Loadbalancer.org Ltd. www.loadbalancer.org +1 888 867 9504 / +44 (0)330 380 1064

Re: Traffic delivered to disabled server when cookie persistence is enabled after upgrading to 1.8.1

2017-12-20 Thread Greg Nolle
Hi Andrew, I can’t find any reference to a “HALTED” status in the manual. I’m *not* referring to “DRAIN” though (which I would expect to behave as you describe), I’m referring to "MAINT", i.e. disabling the backend server. Here’s the snippet from the management manual to clarify what I’m

Re: Traffic delivered to disabled server when cookie persistence is enabled after upgrading to 1.8.1

2017-12-20 Thread Andrew Smalley
Hi Greg You say traffic still goes to the real server when in MAINT mode, Assuming you mean DRAIN Mode and not HALTED then this is expected. Existing connections still goto a server while DRAINING but no new connections will get there. If the real server is HALTED then no traffic gets to it.