[Bug 1209518] New: config file from samba-ad-dc causes error on named (bind) start
https://bugzilla.suse.com/show_bug.cgi?id=1209518 Bug ID: 1209518 Summary: config file from samba-ad-dc causes error on named (bind) start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers@SuSE.de Reporter: mkubecek@suse.com QA Contact: samba-maintainers@SuSE.de Found By: --- Blocker: --- After an upgrade from Leap 15.4 to (beta) 15.5, then named daemon (bind) fails to start with the following error:
named.service: Failed to set up mount namespacing: /run/systemd/unit-root/var/lib/samba/bind-dns: No such file or directory
While searching for the errror, I found https://forums.opensuse.org/t/bind-broken-after-zypper-dup/144767/2 The path in question is in /usr/lib/systemd/system/named.service.d/26-samba-dlz.conf which belongs to samba-ad-dc package. Based on the suggestion from the forum, I tried to shadow this file with /etc/../26-samba-dlz.conf where I prefixed the path with "**-**". This seemed to work well but today bind failed to start again, this time with
/etc/systemd/system/named.service.d/26-samba-dlz.conf:2: ReadWritePaths= path is not absolute, ignoring: **-**/var/lib/samba/bind-dns
As I'm not familiar with the way systemd handles mount namespaces and I do not really need or want Samba AD or anything related to it, I tried to uninstall the samba-ad-dc package; now named starts without any issue. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209518
https://bugzilla.suse.com/show_bug.cgi?id=1209518#c1
Samuel Cabrero
After an upgrade from Leap 15.4 to (beta) 15.5, then named daemon (bind) fails to start with the following error:
named.service: Failed to set up mount namespacing: /run/systemd/unit-root/var/lib/samba/bind-dns: No such file or directory
While searching for the errror, I found
https://forums.opensuse.org/t/bind-broken-after-zypper-dup/144767/2
The path in question is in
/usr/lib/systemd/system/named.service.d/26-samba-dlz.conf
which belongs to samba-ad-dc package. Based on the suggestion from the forum, I tried to shadow this file with /etc/../26-samba-dlz.conf where I prefixed the path with "**-**". This seemed to work well but today bind failed to start again, this time with
/etc/systemd/system/named.service.d/26-samba-dlz.conf:2: ReadWritePaths= path is not absolute, ignoring: **-**/var/lib/samba/bind-dns
As I'm not familiar with the way systemd handles mount namespaces and I do not really need or want Samba AD or anything related to it, I tried to uninstall the samba-ad-dc package; now named starts without any issue.
Will be fixed by next samba-ad-dc update. *** This bug has been marked as a duplicate of bug 1205946 *** -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com