Currently, if haproxy tries to start up and a webserver is down (and
it's defined as a hostname in the config file) haproxy refuses to
start. Looking at the previous change logs and announcements it seems
this is by design. Why is this done and is there a way to circumvent
this?
Cheers
On 27 April 2012 21:37, Andres Thomas Stivalet atstiva...@gmail.com wrote:
Currently, if haproxy tries to start up and a webserver is down (and
it's defined as a hostname in the config file) haproxy refuses to
start.
Do you really mean down, or unresolvable as per your subject line?
--
Hi,
The only moment HAProxy tries to resolve the IP of a hostname found in
the conf is at startup.
So if it can't find a way to reach the server at this moment, then
HAProxy refuses to startup because it knows he will never be able to
reach it.
Note, there may be some improvement on this point
3 matches
Mail list logo
