Benedikt Spranger wrote on 10/03/2023:
> On Fri, 10 Mar 2023 15:04:44 +0100
> Paride Legovini wrote:
>
>> I am not running sysv systems; The case looks simple enough for me to
>> tempt a fix, but I need validation from an actual sysv user. Even better
>> if you can submit a salsa MR, which will
On Fri, 10 Mar 2023 15:04:44 +0100
Paride Legovini wrote:
[...]
> 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,
Control: severity -1 normal
bene wrote on 08/03/2023:
> On Wednesday, March 08, 2023 20:15 CET, Andreas Hasenack
> 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
On Wednesday, March 08, 2023 20:15 CET, Andreas Hasenack
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
Hi,
what's the actual apparmor DENIED message you get in the logs? Check
`dmesg`.
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.
> 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.
OK. Do it again:
1) Purge kea-dhcp4-server from the system to ensure a clean install
# apt-get purge kea-dhcp4-server
2) Ensure
Benedikt Spranger wrote on 08/03/2023:
> Package: kea-dhcp4-server
> Version: 2.2.0-5
> Severity: important
> X-Debbugs-Cc: none, Benedikt Spranger
>
> Dear maintainer,
>
> after an update kea-dhcp4 refuses to start due to an apparmor
> missconfiguration. To track down the problem I started the
Hi,
On Wed, Mar 8, 2023 at 1:33 AM Benedikt Spranger wrote:
> After adopting /etc/apparmor.d/usr.sbin.kea-dhcp4 by adding
> "owner /run/kea/logger_lockfile rwk,":
>
>
This rule exists in the apparmor profile already:
Package: kea-dhcp4-server
Version: 2.2.0-5
Severity: important
X-Debbugs-Cc: none, Benedikt Spranger
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
9 matches
Mail list logo
