Baptiste,
at first, sorry, I meant to say hi, but I had a very long night and it
seems I have missed it.
About the html. Thunderbird has a default html and txt message setting
by default, normaly I change that, but as I said, I had a long night.
The next time I'll remember that.
Concerning the load balancing, I have experience with load balancing,
and yes I knew it was a backend Problem. Most of the backends have been
shown as down in my stats, as I already written in my last message. The
only thing I thought strange was, that one was shown up and still got me
that 503 error.
About that debugging, that was the question. How much information does
HAProxy provide to find the error concerning those backend health checks
and shuting down those systems.
I've set the log to debug mode but everything I got were this sort of
log entries:
Aug 30 09:48:49 localhost haproxy[17568]: Connect from
81.44.136.142:54570 to 192.168.48.12:80 (www.adworxs.net-merged/HTTP)
So I couldn't find the reason, why all the backends have been shutdown.
Obviously cause the check thought they were not availabe, but the
problem is, that the same configuration has been working already.
I had a network problem yesterday and had to reboot those haproxy
systems, since that moment none of the websites configured did work
anymore.
So my question was, which log interface gives me the correct information
about the checks and what would be the best way to analyze this problem.
Thank you so far.
Best regards
Sebastian
On 30.08.2013 07:38, Baptiste wrote:
Sebastian,
1. when you talk to a ML, you should say 'Hi'
2. when you talk to a ML, you shouldn't send HTML mails
Now, I can see you have absolutely no experience with Load-Balancing.
Here are a few clues for you:
- when you have a 503 error, then no need to think, it means ALL the
servers from the farm are seen DOWN
- the purpose of the health check is to ensure the service is UP and
RUNNING on the servers
- Usually, it is a good idea to enable health checking when
load-balancing, to allow haproxy to know server status to avoid
sending client requests to dead servers
- instead of disabling health checking, you should be troubleshooting
it: HAProxy logs will tell you why the health check was not working.
Good luck,
Baptiste
On Fri, Aug 30, 2013 at 6:19 AM, Sebastian Fohler<[email protected]> wrote:
Ok, I disabled the health check and it's working now, so it's definitly a
problem of haproxy shuting down the backends.
On 30.08.2013 05:55, Sebastian Fohler wrote:
Some help, would be to disable the health check for the time being, is that
possible.
At least it would be a quickfix.
On 30.08.2013 05:25, Sebastian Fohler wrote:
Is there some simple way to find out why I get this error from my haproxy
cluster?
503 Service Unavailable
No server is available to handle this request.
It looks like all my backend servers are down. Even in pools which are shown
as up in my stats.
How can I debug that sensible?
Thank you in advance.
Best regards
Sebastian
