> Ah you really want to find another bug! :-) But of course! :-)
Actually, I think I did find one while narrowing down the cause for the previous bug. I can trigger a segfault with this config: default-server ca-file ca-bundle.crt resolvers default inter 5s fastinter 2s downinter 10s init-addr libc,last check ssl verifyhost sermonaudio.com pool-purge-delay 20s max-reuse 900 alpn h2,http/1.1 check-alpn http/1.1 backend problematic_precursor option httpchk GET /healthz mode tcp # Static for now server master-00 <ip>:6443 no-ssl check-ssl verify none server master-01 <ip>:6443 no-ssl check-ssl verify none server master-02 <ip>:6443 no-ssl check-ssl verify none backend problematic option httpchk GET /healthz mode tcp # Static for now server master-2-00 <ip>:6443 no-ssl check-ssl verify none server master-2-01 <ip>:6443 no-ssl check-ssl verify none server master-2-02 <ip>:6443 no-ssl check-ssl verify none The log: Jun 19 08:47:19 ha-balancer-01 haproxy[10320]: Proxy problematic started. Jun 19 08:47:19 ha-balancer-01 haproxy: [ALERT] 169/084719 (10320) : Current worker #1 (10322) exited with code 139 (Segmentation fault) I suspect this should probably be a config error, since alpn or check-alpn is being used on TCP via the defaults and causing a segfault, but I'm not sure. This is definitely not priority, as removing it from defaults and putting it directly on the servers that need it works. Best, Luke — Luke Seelenbinder SermonAudio.com <http://sermonaudio.com/> | Senior Software Engineer > On Jun 19, 2019, at 10:03, Willy Tarreau <[email protected]> wrote: > > On Wed, Jun 19, 2019 at 09:57:43AM +0200, Luke Seelenbinder wrote: >> Hi Willy, >> >> Just updated, and I can confirm, those fixes worked. > > Great, thanks for the quick feedback. > >> I had seen the commits in git, but didn't think they'd apply--thanks for >> pointing me back to them! >> >> I'm looking forward to all the other goodies we can deploy in 2.0.0! :-) > > Ah you really want to find another bug! :-) > > Willy >
