Server/backend DOWN log messages

Help!
1

Hello All,

We have a few instances of HA Proxy running that we noticed weren’t logging server/backend up/down messages, e.g.

Jan 13 15:15:47 RULE-NB-014 systemd[1]: Started HAProxy Load Balancer.
Jan 13 15:15:48 RULE-NB-014 haproxy[17461]: [WARNING] 012/151548 (17461) : Server dynamic/dynsrv2 is DOWN, reason: Layer7 wrong status, code: 40>
Jan 13 15:15:48 RULE-NB-014 haproxy[17461]: [WARNING] 012/151548 (17461) : Server static/statsrv1 is DOWN, reason: Layer4 timeout, check duratio>
Jan 13 15:15:48 RULE-NB-014 haproxy[17461]: [WARNING] 012/151548 (17461) : Server static/statsrv2 is DOWN, reason: Layer4 timeout, check duratio>
Jan 13 15:15:48 RULE-NB-014 haproxy[17461]: [ALERT] 012/151548 (17461) : backend ‘static’ has no server available!
Jan 13 15:15:48 RULE-NB-014 haproxy[17461]: [WARNING] 012/151548 (17461) : Server dynamic/dynsrv1 is DOWN, reason: Layer4 timeout, check duratio>
Jan 13 15:15:49 RULE-NB-014 haproxy[17461]: [WARNING] 012/151549 (17461) : Server dynamic/dynsrv3 is DOWN, reason: Layer4 timeout, check duratio>
Jan 13 15:15:49 RULE-NB-014 haproxy[17461]: [WARNING] 012/151549 (17461) : Server dynamic/dynsrv4 is DOWN, reason: Layer4 timeout, check duratio>
Jan 13 15:15:49 RULE-NB-014 haproxy[17461]: [ALERT] 012/151549 (17461) : backend ‘dynamic’ has no server available!

We are running HA Proxy version 1.8.27 on these servers. On the servers where it does work we are running 2.4.17. I’ve tested various HA Proxy versions and it seems that this type of logging should be enabled by default, this seem to be the case for 1.9.X*, 2.0.X* and 2.4.X.

I’ve tried playing with the logging config of a 1.8.27 instance but I cannot get it log the above messages. Is anyone aware if there was a bug or a change in behaviour here?

Regards,

Rhys

2

Hello,

1.8 is EOL and unmaintained since Q4 2022 (version 1.8.31). I’m afraid we will not be able to support 1.8.

I do not recall such bugs or changes specifically, but that doesn’t mean much, it was a long time ago.

2.4 is the newest software train you mention, yet it is already in critical fixes only mode and will be EOL in 2026-Q2.

I recommend checking haproxy.org for an overview. Currently I would recommend the latest bugfix release of 3.2 which will be supported until 2030.

3

OK. I was half expecting that as an answer. Yes, we are running an ancient version and shoul dget that upgraded. Thanks.

Rhys