Re: DNS resolution problem since 1.8.14

2018-12-24 Thread Patrick Valsecchi
... J On Sun, 23 Dec 2018 at 16:17, Patrick Valsecchi <mailto:patr...@thus.ch>> wrote: I did a tcpdump. My config is modified to point to a local container (www) in a docker compose (I'm trying to simplify my setup). You can see the DNS answers correctly: 16:06:00.18153

DNS resolution problem since 1.8.14

2018-12-23 Thread Patrick Valsecchi
Hi, Since haproxy version 1.8.14 and including the last 1.9 release, haproxy puts all my backends in MAINT after around 31s. They first work fine, but then they are put in MAINT. The logs look like that: <149>Dec 23 12:45:11 haproxy[1]: Proxy www started. <149>Dec 23 12:45:11

Re: DNS resolution problem since 1.8.14

2018-12-23 Thread Patrick Valsecchi
> localhost.40994: 63037 1/0/0 www. A 172.20.0.17 (40) Could it be related to that? https://github.com/haproxy/haproxy/commit/8d4e7dc880d2094658fead50dedd9c22c95c556a On 23.12.18 13:59, Patrick Valsecchi wrote: Hi, Since haproxy version 1.8.14 and including the last 1.9 release, hapr