Public bug reported:
When I run:
systemctl start haproxy
from a fresh installation, everything works as expected.
If I create an AppArmor profile and set HAProxy in complain mode:
systemctl stop haproxy
aa-autodep /usr/sbin/haproxy
aa-complain /usr/sbin/haproxy
systemctl start haproxy
HAProxy hangs and timeout.
It seems that systemd can't notify the service has started anymore.
Just kill the service and disable AppArmor makes it work again:
aa-disable /usr/sbin/haproxy
systemctl restart haproxy
I have the same behaviour on Redis.
lsb_release -rd
Description: Ubuntu 26.04 LTS
Release: 26.04
apt-cache policy apparmor
apparmor:
Installed: 5.0.0~beta1-0ubuntu7
Candidate: 5.0.0~beta1-0ubuntu7
Version table:
*** 5.0.0~beta1-0ubuntu7 500
500 https://archive.ubuntu.com/ubuntu resolute/main amd64 Packages
100 /var/lib/dpkg/status
apt-cache policy haproxy
haproxy:
Installed: 3.2.9-1ubuntu2.2
Candidate: 3.2.9-1ubuntu2.2
Version table:
*** 3.2.9-1ubuntu2.2 500
500 https://archive.ubuntu.com/ubuntu resolute-updates/main amd64
Packages
500 https://security.ubuntu.com/ubuntu resolute-security/main amd64
Packages
100 /var/lib/dpkg/status
3.2.9-1ubuntu2 500
500 https://archive.ubuntu.com/ubuntu resolute/main amd64 Packages
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Tags: apparmor complain notify timeout
** Attachment added: "apport.apparmor.zh6tz120.apport"
https://bugs.launchpad.net/bugs/2162790/+attachment/5989329/+files/apport.apparmor.zh6tz120.apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2162790
Title:
Complain mode causes notify services to not start properly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2162790/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
