Ok, I have a reproducer. What triggers this behavior is the rsyslog
restart, not haproxy.
When haproxy is upgraded or reinstalled (the package), it does restart,
but it also touches the rsyslog snipped config at
/etc/rsyslog.d/49-haproxy.conf. This triggers a restart of rsyslog
itself via dpkg triggers, and that causes the problem.
To reproduce, just restart rsyslog. After this, haproxy logging will be
broken until haproxy itself is restarted:
[Tue Mar 3 14:00:54 2026] audit: type=1400 audit(1772546453.881:137):
apparmor="DENIED" operation="sendmsg" class="file" info="Failed name
lookup - disconnected path" error=-13 profile="rsyslogd"
name="var/lib/haproxy/dev/log" pid=5137 comm="haproxy"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
** Changed in: haproxy (Ubuntu)
Status: Confirmed => In Progress
** Changed in: haproxy (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2138647
Title:
haproxy stops logging after reload with permission denied error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/2138647/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
