Hi Cyril, It’s only taken me 2 months to upgrade!
Once I figured out the process I dove straight in at the deep end and went up to 1.6.9, it's been live a few days now without issues so I have enabled health checking tonight on the nodes that were mis-reporting being down and they are showing green! Thank you for your help, and excellent work on the new HTML documentation, the format is much more readable than the txt version for occasional users like me. Kind Regards, John Lanigan -----Original Message----- From: John Lanigan [mailto:[email protected]] Sent: Monday 8 August 2016 06:25 To: Cyril Bonté Cc: [email protected] Subject: RE: Problem with health checking Thanks Cyril, I'll try that, and also have the app server team compare their settings across the servers. Kind Regards, John Lanigan -----Original Message----- From: Cyril Bonté [mailto:[email protected]] Sent: Sunday 7 August 2016 20:28 To: John Lanigan Cc: [email protected] Subject: Re: Problem with health checking Hi John, Le 07/08/2016 à 21:17, John Lanigan a écrit : > [...] > http-check expect status 200 > http-check disable-on-404 > > server hostingapp2_5041 172.17.2.40:5041 check > server hostingapp3_5041 172.17.2.50:5041 check > > [...] > > If I access all four of those URLs with lynx to show the headers from > the command line on the haproxy server I get the same result from each > server, instantaneous response and HTTP 200 status. > > [...] > > But the haproxy stats page reports L7 timeout if we add in a check on > the new app setup. > > > > Any ideas what I need to check next? > > [...] > > I’ve been running haproxy 1.4.24 on centos 6.5 for over 2 years, load > balancing a pair of Oracle 11g app servers on Windows 2008r2. Did you upgrade to the latest 1.4 to see if the issue remains ? After reviewing the changelog with the configuration you have provided, I think it comes from your http-check rules, due to a bug that has been fixed in 1.4.26 (about HTTP keep-alived connections with http-check) : http://www.haproxy.org/git?p=haproxy-1.4.git;a=commit;h=98739cba6281adeaf1db26be188970e4423b51fc As a quick test, maybe you can disable keep-alive on your servers to verify this. -- Cyril Bonté
