Thanks Cyril, I'll try that, and also have the app server team compare their settings across the servers.
Kind Regards, John Lanigan CORE | +353 (0)25 41400 | ||john.lani...@coresoftware.ie | www.coresoftware.ie -----Original Message----- From: Cyril Bonté [mailto:cyril.bo...@free.fr] Sent: Sunday 7 August 2016 20:28 To: John Lanigan Cc: haproxy@formilux.org 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é
