What URL does haproxy use exactly to check the service? Is it the realm + the url part or something else? Just to be sure to test the correct option.
Best regards Sebastian On 10.02.2012 09:56, Baptiste wrote:
Hi, Maybe you're server require a Host header in the health check. Have you tried running the check using wget or curl on the server IP address? cheers On Fri, Feb 10, 2012 at 9:00 AM, Sebastian Fohler<[email protected] <mailto:[email protected]>> wrote: Hi Is there some way to check the backendservers manually? I'm always get this errors: Feb 9 13:42:56 haproxy[57652]: Server adserver.dev.adworxs.net/adserver1.dev <http://adserver.dev.adworxs.net/adserver1.dev> is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. Feb 9 13:59:36 haproxy[57652]: Server adserver.dev.adworxs.net/adserver2.dev <http://adserver.dev.adworxs.net/adserver2.dev> is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue. But can't find out why. Log doesn't show me more informations and just calling the server seem to show no such 404 errors. It must be something between haproxy and my backend system. I've configured very long timeouts and nearly half that long check times but still the same problem. For some reason the physical servers are sending a 404 and after that haproxy shuts them down. They work called by haproxy without any trouble until the check followed by a shutdown. Best regards Sebastian
-- Sebastian Fohler Far-Galaxy Networks Web: http://www.far-galaxy.de Tel.: +49 (0)173 8796211 E-Mail: [email protected]
