Hi Jonathan,
I've build the 1.8.16 image myself and the problem is indeed fixed. Any
plan of including that fix in a 1.9.1 release?
Thanks.
On 23.12.18 18:20, Jonathan Matthews wrote:
Hey Patrick,
Have you looked at the fixes in 1.8.16? They sound kinda-sorta related
to your problem ...
Hey Patrick,
Have you looked at the fixes in 1.8.16? They sound kinda-sorta related to
your problem ...
J
On Sun, 23 Dec 2018 at 16:17, Patrick Valsecchi 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
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.181533 IP (tos 0x0, ttl 64, id 63816, offset 0, flags [DF],
proto UDP (17), length 68)
127.0.0.11.53 >
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
4 matches
Mail list logo
