Hi, > I am having trouble with Haproxy using a configuration was previously > worked and am getting a very odd to me error > > > > Jan 11 13:58:00 ca04vlhaproxy01 haproxy[16077]: [ALERT] 010/135800 > (16077) : Proxy 'graylog_back': unable to find required default_backend: > '#002'.
You might want to manually update your haproxy from the tip of 2.2 branch while waiting for a new version: A regression only affecting 2.2.26 was recently discovered (see below), and the fix is available on top of 2.2.26 (https://git.haproxy.org/?p=haproxy-2.2.git;a=commit;h=a7d662bda95c33131126b2ad45bbb073d93b85d3) Regards, Aurelien > On 05/01/2023 14:44, Christopher Faulet wrote: >> Le 1/5/23 à 13:20, Julien Thomas a écrit : >>> Hello, >>> >>> I have an issue with haproxy 2.2.26 that I do not have in 2.2.25, it >>> seams to be related to the ring object I use in my configuration for >>> logs. >>> >>> I do not think it is due to my build >>> (https://github.com/zenetys/rpm-haproxy/commits/haproxy22z) because we >>> did not change it in that branch. >>> >>> I get "unable to find required use_backend: ''" errors. >>> >>> [root@zelk-prod-01 haproxy]# haproxy -f >>> /etc/haproxy/haproxy-extract.cfg -c >>> [NOTICE] 004/130824 (2015177) : haproxy version is 2.2.26-97059ba >>> [NOTICE] 004/130824 (2015177) : path to executable is /usr/sbin/haproxy >>> [ALERT] 004/130824 (2015177) : Proxy 'ft_rsyslog_514': unable to find >>> required use_backend: ''. >>> [ALERT] 004/130824 (2015177) : Fatal errors found in configuration. >>> >> >> Thanks for the report! Indeed, there is a bug, specific to the 2.2.26. A >> regression was introduced when the commit 7af321580 ("BUG/MEDIUM: sink: >> bad init sequence on tcp sink from a ring.") was backported. >> >> I pushed a fix. > > Thank you Christopher, it's working like a charm with your patch 😉 > > Julien >
