Op 12-02-19 om 00:21 schreef Bernhard Schmidt:
> Sorry, had a typo in it (_default.nzd.lock vs. _default.nzd-lock).
> Please change the filename in /etc/apparmor.d/local/usr.sbin.named to
> match the name of the file not being accessible and reload the profile.
>
> That worked in my quick test.
I
Am 12.02.19 um 00:05 schrieb Paul van der Vlis:
/var/cache/bind/_default.nzd.lock rwk,
>>>
>>> With " rwk," at the end?
>>
>> Yes, that means "read write lock", which according to the log you showed
>> was the denied operation.
>>
>>> When I do "aa-enforce /usr/sbin/named", then I cannot star
Op 11-02-19 om 23:49 schreef Bernhard Schmidt:
> Am 11.02.19 um 23:32 schrieb Paul van der Vlis:
>
> Hi Paul,
>
> please keep the Bug CCed...
Ah, sorry.
I upgraded from Debian9 tot Debian10 (testing). After this, bind did not
start. Syslog says it's AppArmor (see syslog below).
>
Am 11.02.19 um 23:32 schrieb Paul van der Vlis:
Hi Paul,
please keep the Bug CCed...
>>> I upgraded from Debian9 tot Debian10 (testing). After this, bind did not
>>> start. Syslog says it's AppArmor (see syslog below).
>>>
>>> A work-arround is "aa-complain /usr/sbin/named".
>>> You need the pac
Am 11.02.19 um 18:01 schrieb Paul van der Vlis:
Dear Paul,
> I upgraded from Debian9 tot Debian10 (testing). After this, bind did not
> start. Syslog says it's AppArmor (see syslog below).
>
> A work-arround is "aa-complain /usr/sbin/named".
> You need the package apparmor-utils for that.
Are y
Package: bind9
Version: 1:9.11.5.P1+dfsg-1
Severity: normal
I upgraded from Debian9 tot Debian10 (testing). After this, bind did not
start. Syslog says it's AppArmor (see syslog below).
A work-arround is "aa-complain /usr/sbin/named".
You need the package apparmor-utils for that.
With regards,
P
6 matches
Mail list logo
