jayjay73
(Jerome Rabas)
27 May 2026 13:43
1
Hello
I have a little problem with HAProxy logging. It seems HAProxy sends correctly logs to Syslog, but they are not written to disk.
My HAProxy is configured to send log to Syslog :
global
log 127.0.0.1 local1
If I check what is sent to Syslog with tcpdump -i lo udp port 514 -v, I can see HAproxy logs:
tcpdump: listening on lo, link-type EN10MB (Ethernet), snapshot length 262144 bytes
15:33:51.326605 IP (tos 0x0, ttl 64, id 15535, offset 0, flags [DF], proto UDP (17), length 258)
localhost.localdomain.58915 > localhost.localdomain.syslog: SYSLOG, length: 230
Facility local1 (17), Severity info (6)
Msg: May 27 15:33:51 haproxy[30542]: xx.xx.xx.xx:64268 [27/May/2026:15:33:51.316] http-in~ backend_jellyfin/web-server1 0/0/1/8/9 204 111 - - ---- 2/2/1/1/0 0/0 "POST…….
But I have no logs in /var/log/messages.
Any idea?
I am not very knowledgeable on syslog settings but the IPFire config settings are
https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=config/etc/syslog.conf;hb=81af070d7c62476dc5e9c6a39a271077a9a74bd1
which refers to local0, local2 and local5.
Maybe local1 is not used.
Maybe change your haproxy settings from local1 to local2
EDIT:
The example haproxy config for SMTP failover use local2
https://www.ipfire.org/docs/addons/haproxy
jayjay73
(Jerome Rabas)
27 May 2026 14:40
3
I tried both local1 and local2, and it is the same: HAProxy connect to Syslog to send logs, but nothing is written in /var/log/messages or /var/log/haproxy
Then there is probably something else that needs to be defined differently but I can’t help with that as I haven’t used haproxy.
There are other users in the community that do use it so there should be further input to give you pointers on what to modify.
Maybe provide a copy of the haproxy configuration file you are using, with any sensitive aspects redacted.
jayjay73
(Jerome Rabas)
27 May 2026 16:58
5
It seems nothing is listening UDP 514: ss -lunp | grep 514 doesn’t return anything
I find a workaround, but it is not the best solution:
In the global section, I changed to log /dev/log local0 (instead of the IP address)
I had to comment chroot /var/lib/haproxy
i don’t understand why it was working before my last update.
jayjay73
(Jerome Rabas)
5 June 2026 08:44
6
It is confirmed in this thread that syslogd is not listening on port 514: Syslogd no longer listening on port 514?