Hi Baptiste, could you please have a look at this one, I suspect Raghu's proposal is reasonable, I just want to be sure we don't break DNS and friends.
Thanks, Willy On Mon, Aug 13, 2018 at 08:16:31PM +0530, Raghu Udiyar wrote: > Hi Willy, Baptiste > > On Fri, 29 Jun 2018 at 08:12 Willy Tarreau <[email protected]> wrote: > > > Hi Raghu, > > [...] > > > > [ALERT] 248/130258 (21960) : parsing [/etc/haproxy/test.cfg:53] : > > 'server bla' : no method found to resolve address '(null)' > > [ALERT] 248/130258 (21960) : Failed to initialize server(s) addr. > > > > According to Nenad : > > "It's not a good way to fix the issue we were experiencing > > before. It will need a bigger rewrite, because the logic in > > srv_iterate_initaddr needs to be changed." > > > > Could you please try the example above in the commit message with and > > without > > your patch ? Maybe the problem is still there, or maybe the logic change > > mentioned by Nenad has already been done and this is no longer a problem, > > in which case we could take your patch this time. > > > > Yes this is a problem - I missed to test this case. I have a proposal. > > The init-addr option only makes sense when fqdn is used. But last method is > useful when using IP addresses. This patch enables > the last method to work by default when IP addresses are used. Can you > please review? > > Thanks > Raghu
