Re: Permission error after upgrade to Debian Buster (10.2)
"Kaulkwappe" <[email protected]> Mon, 25 Nov 2019 01:34:51 +0100
| Newsgroups | gmane.network.dns.nsd.general |
|---|---|
| Message-ID | <[email protected]> |
--ad7e475e8d05bb98ceacb4f357bc22aec0c3e2be3354bce1936b5a228d6c036f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div style=3D"font-family: Arial; text-align: left; font-size: 14px; color:= #000000;">> [...] I'd double check if it's indeed effective with "syste= mctl show nsd | grep ReadWritePaths"</div><div style=3D"font-family: Arial;= text-align: left; font-size: 14px; color: #000000;"><br>Seems to be effect= ive:</div><div style=3D"font-family: Arial; text-align: left; font-size: 14= px; color: #000000;">> # systemctl show nsd | grep ReadWritePaths</= div><div style=3D"text-align: left;"><span style=3D"font-size: 14px;">> = ReadWritePaths=3D/var/lib/nsd /var/log /etc/nsd /run</span></div><div style= =3D"text-align: left;"><span style=3D"font-size: 14px;"><br></span></div><d= iv style=3D"text-align: left;"><span style=3D"font-size: 14px;">The problem= with the log file will never stop the NSD service from working (I believe)= but the log file is quite important, so, of course, NSD should be able to = append to it.</span></div><div style=3D"text-align: left;"><span style=3D"f= ont-size: 14px;"><br></span></div><div style=3D"text-align: left;"><span st= yle=3D"font-size: 14px;">Does anyone already had this problem after an upgr= ade?</span></div><div style=3D"text-align: left;"><span style=3D"font-size:= 14px;"><br></span></div><div style=3D"text-align: left;"><span style=3D"fo= nt-size: 14px;">Kind Regards,</span></div><div style=3D"text-align: left;">= <span style=3D"font-size: 14px;">Kaulkwappe</span></div><div style=3D"text-= align: left;"><span style=3D"font-size: 14px;"><br></span><br><hr style=3D"= color: rgb(0, 0, 0); font-family: Arial; font-size: 14px; border-width: 0px= 0px 1px; border-top-style: initial; border-right-style: initial; border-le= ft-style: initial; border-top-color: initial; border-right-color: initial; = border-left-color: initial; border-image: initial; border-bottom-style: sol= id; border-bottom-color: rgb(218, 218, 218);"><b style=3D"color: rgb(0, 0, = 0); font-family: Arial; font-size: 14px;">From:</b><span style=3D"font-size= : 14px;"> Simon Deziel <</span><a href=3D"/email/new/1/simon%40sdeziel.i= nfo" style=3D"color: rgb(0, 0, 0); font-family: Arial; font-size: 14px;">si= [email protected]</a><span style=3D"font-size: 14px;">></span><br><b styl= e=3D"color: rgb(0, 0, 0); font-family: Arial; font-size: 14px;">Sent:</b><s= pan style=3D"font-size: 14px;"> Monday, 25. Nov 2019 =E2=80=93 01:26 CET += 0100</span><br><b style=3D"color: rgb(0, 0, 0); font-family: Arial; font-si= ze: 14px;">To:</b> <a href=3D"/email/new/1/nsd-users%40NLnetLabs.nl" style= =3D"color: rgb(0, 0, 0); font-family: Arial; font-size: 14px;">nsd-users@NL= netLabs.nl</a><br><br><b style=3D"color: rgb(0, 0, 0); font-family: Arial; = font-size: 14px;">Subject:</b><span style=3D"font-size: 14px;"> Re: [nsd-us= ers] Permission error after upgrade to Debian Buster (10.2)</span><br><br><= /div><div>=0A=09=09=09=09=0A=09=09=09=09=09<style>=0A=09=09=09=09=09=09=0A= =09=09=09=09=09=09body {=0A=09=09=09=09=09=09=09font-family: "Arial";=0A=09= =09=09=09=09=09=09font-size: 100% !important;=0A=09=09=09=09=09=09=09margin= : 0;=0A=09=09=09=09=09=09=09line-height: 1.2rem;=0A=09=09=09=09=09=09}=0A= =09=09=09=09=09=09=0A=09=09=09=09=09</style>=0A=0A=09=09=09=09=09<pre style= =3D"white-space: pre-wrap; color: #173860;">On 2019-11-24 6:10 p.m., Kaulkw= appe wrote:=0A> Hi Simon,=0A> =0A> > I would have expect a per= mission error instead of a "read-only" one. It=0A> > looks as if /va= r/log was not properly added to be ReadWritePaths set.=0A> =0A> That = is what I have used:=0A> > ReadWritePaths=3D/var/lib/nsd /var/log /e= tc/nsd /run=0A=0ANot sure what would explain the read-only error then. I'd = double check=0Aif it's indeed effective with "systemctl show nsd | grep Rea= dWritePaths"=0A=0A> > This unlink failure is expected and AFAICT har= mless.=0A> It should be harmless, but it doesn't look nice. I would cons= ider this as a bug.=0A=0AAgreed. Interestingly, unbound accepts "-p" to ski= p managing its own=0APID. If nsd could get this, it would be handy when man= aging the daemon=0Awith systemd.=0A=0A> > I believe that xfrd.state = should be owned by nsd:nsd as the daemon needs=0A> > to write to tha= t file.=0A> After changing the owner to nsd:nsd I believe this problem i= s fixed. Thanks!=0A=0AGlad to hear that!=0A=0ARegards,=0ASimon=0A__________= _____________________________________=0Ansd-users mailing list=0Ansd-users@= NLnetLabs.nl=0Ahttps://open.nlnetlabs.nl/mailman/listinfo/nsd-users=0A</pre= >=09=09=09=09=09=0A=09=09=09=09</div> --ad7e475e8d05bb98ceacb4f357bc22aec0c3e2be3354bce1936b5a228d6c036f Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ nsd-users mailing list [email protected] https://open.nlnetlabs.nl/mailman/listinfo/nsd-users --ad7e475e8d05bb98ceacb4f357bc22aec0c3e2be3354bce1936b5a228d6c036f--