Hi, On Fri, May 11, 2012 at 10:32:33PM +0200, Baptiste wrote: > On Fri, May 11, 2012 at 6:09 PM, 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. 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? > > > > I would consider this a rather large design flaw, I must be missing > > something. > > > > Cheers > > > > Hi, > > Is the hostname resolvable when the server is down? > > For now, HAProxy only tries to resolve a hostname at start up.
I think there is some misunderstanding somewhere, Andreas. As Baptiste says, haproxy resolves hostnames at start up. This has been the case forever, since the first ever version 12 years ago, so I don't know what change log announcement makes you think there was a change on this behaviour. Also, the fact that the server is down is irrelevant to the fact that it does not resolve. > Willy has plans to improve this by doing a name lookup during health > checks, allowing a server to change its IP address. Maybe it ill fix > the issue you're describing. Well, I must say I'm unsure what we'll do upon startup, because if we accept to start with buggy host names, a number of admins will get trapped with errors in their configs causing servers to remain down forever. At least right now they know from the beginning that they have to fix their configs. Maybe we'll have to support a per-backend option to enable delayed host name resolution, I don't know yet. Regards, Willy
