Hi Veiko, On Fri, Jun 16, 2017 at 01:41:14PM +0300, Veiko Kukk wrote: > > So I have more info on this now. Veiko, first, I'm assuming that your config > > was using "resolvers dns_resolvers" on the "server" line, otherwise > > resolvers > > are not used. > > My real world configs use resolvers, but timeouts happen even when resolver > was not used anywhere.
Wow then that's super strange, as by definition they are not even triggered in this case! (...) > > BTW, (probably that it was just for illustration purpose), but please don't > > use well-known services like google, yahoo or whatever for health checks. If > > everyone does this, it will add a huge useless load to their servers. > > It was just that anybody could use simple trimmed down configuration for > quick testing. Real configuration has no need for having google.com as > backend and is much more complex. OK, I easily understand and appreciate this. For now I couldn't reproduce the issue at all on 1.6.12 so that's why I suspected there were some other differences. > This exact configuration can be easily used to test 1.6.12 - a simple reload > would cause two first google.com checks to fail with timouts. Also any > requests against ssl-frontend will fail few first checks after reload. I think I overlooked that part about the reload being needed for the issue to happen. I'll try again with a reload. Thanks for all the precisions, Willy
