Hi,
I'm working on bind/named and I'm currently trying to find out why
starting of named fails.
When I run "systemctl start named", I get these lines in the journal:
Oct 22 09:02:05 sles15-sp4 systemd[2012]: Failed to determine whether
/run/systemd/unit-root/run/named is already a mount point:
No such file or directory
Oct 22 09:02:05 sles15-sp4 systemd[2012]: named.service: Failed to set
up mount namespacing: /run/systemd/unit-root/run/named:
No such file or directory
Oct 22 09:02:05 sles15-sp4 systemd[2012]: named.service: Failed at step
NAMESPACE spawning /usr/lib/bind/named.prep: No such
file or directory
and "systemctl status named" reports:
Process: 2012 ExecStartPre=/usr/lib/bind/named.prep (code=exited,
status=226/NAMESPACE)
The /usr/lib/bind/named.prep has not been started.
Our systemd colleague is currently occupied elsewhere, so I am resorting
to this ML. I guess I'm just missing something in the SPEC file and
would appreciate any pointers to where to look.
Thanks and ... stay healthy!
Josef
--
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5
90409 Nürnberg
Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
