Re: Segmentation faults (1.8.4-de425f6 2018/02/26)

Hi Willy, alright, I updated to latest snapshot. Thanks for all your work!

Re: Segmentation faults (1.8.4-de425f6 2018/02/26)

Sorry, here's the stacktrace root@d1e4f8ea5d87:/# haproxy -vv HA-Proxy version 1.8.5 2018/03/23 Copyright 2000-2018 Willy Tarreau Build options : TARGET = linux2628 CPU = generic CC = gcc CFLAGS = -O2 -g -fno-strict-aliasing -Wdeclaration-after-statement -fwrapv -fno-strict-o

Re: Segmentation faults (1.8.4-de425f6 2018/02/26)

After upgrading to 1.8.5 a few days ago haproxy just segfaulted again :/ Willy, do you want to have a new coredump?

Re: Segmentation faults (1.8.4-de425f6 2018/02/26)

> Am 23.03.2018 um 17:59 schrieb Willy Tarreau : > > If you could give 1.8.5 a try, as a few bugs were fixed after the commit > referenced in this thread, that would be great. The commit related to > the bogus buffer wrapping in bi_putblk() could possibly strike on H2 > when receiving POSTs. The

Segmentation faults (1.8.4-de425f6 2018/02/26)

Hi, we had two crashes yesterday within about 2 hours. HA-Proxy version 1.8.4-de425f6 2018/02/26 Copyright 2000-2018 Willy Tarreau Build options : TARGET = linux2628 CPU = generic CC = gcc CFLAGS = -O2 -g -fno-strict-aliasing -Wdeclaration-after-statement -fwrapv -Wno-null-d

Re: 1.8.1 backend stays 'DOWN' when dns resolvers and http health checks are used

> Am 18.12.2017 um 15:52 schrieb Christopher Faulet : > > There have been some fixes since the 1.8.1. One of them could fix your > problem: http://git.haproxy.org/?p=haproxy-1.8.git;a=commit;h=80b92902 > Thanks Christopher, that fi

1.8.1 backend stays 'DOWN' when dns resolvers and http health checks are used

Hi, when I use dns resolvers combined with http health checks, the backend either never goes to 'UP' when haproxy starts before the backend, or the backend stays 'DOWN' when it wasn't resolvable for a while. --> starting haproxy: [WARNING] 348/224658 (10) : Server phoenix-backend/phoenix is D