Benedikt Spranger wrote on 08/03/2023: > Package: kea-dhcp4-server > Version: 2.2.0-5 > Severity: important > X-Debbugs-Cc: none, Benedikt Spranger <b.spran...@linutronix.de> > > Dear maintainer, > > after an update kea-dhcp4 refuses to start due to an apparmor > missconfiguration. To track down the problem I started the server > manualy. No luck. Same error(s) - Therefore further step backs. > Here to reproduce the problem: > > 1) Install kea-dhcp4-server > 2) Start the server manualy: > > # kea-dhcp4 -c /etc/kea/kea-dhcp4.conf > Unable to use interprocess sync lockfile (Permission denied): > /var/run/kea/logger_lockfile
This is expected: in Debian the lockfile path is defined in the systemd service files, like this: Environment="KEA_LOCKFILE_DIR=/run/lock/kea" which is different from the default /var/run/kea/, which got used in your manual attempt. The issue you're seeing is likely not with the lockfile. Running: # KEA_LOCKFILE_DIR=/run/lock/kea kea-dhcp4 -c /etc/kea/kea-dhcp4.conf may show the actual issue, but I suggest using e.g. journalctl -u kea-dhcp4-server.service Please do follow up to this bug if you figure out something more about this issue: if there's a bug in the apparmor profile we want to fix is sooner than later. Thanks!
