Hi Willy,
thank you for answering.
The problem is that the standard health check right now checks the URI
/.../<filename>
But as soon as the jboss backend fails, I get a 503 error page, which
still is responding to the health check.
So the failover I configured does not trigger.
Eighter I must be able to check the jboss directly, with a sepearte
check line or I need the "monitor fail" condition to be set to "if 503
erropage is showing up"
Is that discription better for understanding that problem?
Best regards
Sebastian
On 31.10.2014 09:58, Willy Tarreau wrote:
Hi Sebastian,
On Fri, Oct 31, 2014 at 03:37:39AM +0100, Sebastian Fohler wrote:
Hi Guys,
I've searched the documentation but can't find a condition to set the
"monitor fail" to react to a page with error code 503. I have an apache
server which uses a jboss as proxy backend. So every time the jboss
stops, I have a 503 error page but haproxy does not react to that.
So how can I fix that?
I don't understand well what you're trying to achieve. Either you mean
that jboss is checking haproxy and only supports 503 or you're talking
about health checks in fact. So just to try to narrow down your needs :
- do you want haproxy to test apache/jboss's availability, in which
case you need to configure health checks ;
- or do you want some external components to test haproxy's availability
(in which case it's the monitor fail)
- or maybe a combination of the two ?
Regards,
Willy
