Re: [2.2.9] 100% CPU usage

Hi, I deployed a patched (with volatile hlua_not_dumpable) HAProxy and so far so good, no looping. Christopher I saw new patches with hlua_traceback used instead, looks much cleaner to me, should I verify them instead? :) Christopher & Willy I've forgotten to thank you for help! Kind regards,

Re: [2.2.9] 100% CPU usage

Le 25/03/2021 à 13:38, Maciej Zdeb a écrit : Hi, I deployed a patched (with volatile hlua_not_dumpable) HAProxy and so far so good, no looping. Christopher I saw new patches with hlua_traceback used instead, looks much cleaner to me, should I verify them instead? :) Christopher & Willy I've

[ANNOUNCE] haproxy-2.3.8

Hi, HAProxy 2.3.8 was released on 2021/03/25. It added 22 new commits after version 2.3.7. This version focuses on fixing a few annoying bugs that were reported on 2.3.7 and older, some of which were recent regressions. - Lua: Maciej hit a situation where the watchdog occasionally triggers

Re: OpenSSL Security Advisory

> https://www.openssl.org/support/contracts.html > > OpenSSL 1.1.0 is out of support and no longer receiving updates of any kind. > The impact of these issues on OpenSSL 1.1.0 has not been analysed. > > Users of these versions should upgrade to OpenSSL 1.1.1. > > References >

Fwd: OpenSSL Security Advisory

RL for this Security Advisory: https://www.openssl.org/news/secadv/20210325.txt Note: the online version of the advisory may be updated with additional details over time. For details of OpenSSL severity classifications please see: https://www.openssl.org/policies/secpolicy.html

Re: OpenSSL Security Advisory

[…] > On 25.03.2021., at 17:03, Tim Düsterhus wrote: > […] > > The 'haproxy' image for Docker is maintained by the Docker Official > Images Team [1] [2]. They also handle the necessary rebuilds when the > base image changes. I maintain 2 images as part of the Official Images > program and

is it possible to disable option httpchk per backend?

Hi, is it possible to disable "option httpchk" in specific backend when it is enabled in defaults block? I have config where basically every backend sans one is http so I'd like to keep that in defaults and just disable it in tcp backend (which is backend for SPOE/A) but it seems to be one of

Re: OpenSSL Security Advisory

Paul, On 3/25/21 7:31 PM, Paul Lockaby wrote: > Thanks for all of the responses! So the image version number for HAProxy > stays the same but the hash will update? > Yes exactly. Best regards Tim Düsterhus

Re: OpenSSL Security Advisory

Paul, On 3/25/21 4:46 PM, Paul Lockaby wrote: > As a lurker on this list I've always kind of wondered what the policy is for releasing new containers to address security patches on dependencies like this. I'm not sure who maintains the "official" containers for HAProxy but would they do a

Re: OpenSSL Security Advisory

That would be unfortunate. Some clusters won't be able to distinguish if there is an update or not. That's one reason I typically follow the distro convention of packaging, of tacking onto the tag a -1, so if I need to bump them, it can be. -2 when a new release of the same version comes out.

Re: OpenSSL Security Advisory

Thanks for all of the responses! So the image version number for HAProxy stays the same but the hash will update? > On Mar 25, 2021, at 9:03 AM, Tim Düsterhus wrote: > > Paul, > > On 3/25/21 4:46 PM, Paul Lockaby wrote: >> As a lurker on this list I've always kind of wondered what the policy

Re: OpenSSL Security Advisory

Kevin, On 3/25/21 7:40 PM, Fox, Kevin M wrote: > That would be unfortunate. Some clusters won't be able to distinguish if > there is an update or not. If your toolchain is unable to correctly handle changing tags for Docker Images then it is completely broken. This is happening all the time