Control: severity -1 normal bene wrote on 08/03/2023: > On Wednesday, March 08, 2023 20:15 CET, Andreas Hasenack > <andr...@canonical.com> wrote: > >> I see you are not using the systemd unit, so I suspect you are running kea >> as root directly, instead of as the unprivileged `_kea` user, and you are >> probably tripping over the "owner" flag of the apparmor rules. > > Thanks for the hint... (\me buys some big brown paperbag...) > > It is working now with the following patch to /etc/init.d/kea-dhcp4-server.
> --- /etc/init.d/kea-dhcp4-server.orig 2023-03-08 22:00:35.249600025 > +0100 > +++ /etc/init.d/kea-dhcp4-server 2023-03-08 22:12:11.803979999 +0100 [...] Thanks for the patch. However I have a couple of questions: Are you actually using Bookworm with sysv, having removed systemd, or are you using the init.d scripts for some other reason (integration with other software, habit, ...)? If your init system is systemd, then I strongly advise using systemctl to start/stop/... the daemons. I don't think the init scripts are actively maintained at the moment, as you noticed (FIXME kea team, Cc:). Plus QA on the package (e.g. DEP8 tests) is done assuming systemd. If you are a sysv init user, are you willing to test packages with a candidate fix, before an upload is done? I am not running sysv systems; The case looks simple enough for me to attempt a fix, but I need validation from an actual sysv user. Even better if you can submit a salsa MR, which will also speed up the process of landing a fix: https://salsa.debian.org/debian/isc-kea/ Cheers, Paride
