Right now I'm unable to start my named-chroot.
I've narrowed it down to config files not being mounted correctly to /var/named/chroot/etc
named-chroot.service calles to /lib/systemd/system/named-chroot-setup.service.
Content of this file is standard:
Code: Select all
[Unit] Description=Set-up/destroy chroot environment for named (DNS) BindsTo=named-chroot.service Wants=named-setup-rndc.service After=named-setup-rndc.service [Service] Type=oneshot RemainAfterExit=yes ExecStart=/usr/libexec/setup-named-chroot.sh /var/named/chroot on /etc/named-chroot.files ExecStop=/usr/libexec/setup-named-chroot.sh /var/named/chroot off /etc/named-chroot.files
/usr/libexec/setup-named-chroot.sh /var/named/chroot on /etc/named-chroot.files
it mounts without problems.
When I manually execute:
/usr/libexec/setup-named-chroot.sh /var/named/chroot off /etc/named-chroot.files
it unmounts without problems.
But when I call it:
systemctl start named-chroot-setup.service
it mounts all those files for one second only. Then it instantly dismounts them.
And that's the main reason named-bind won't start because it does named-checkconf after they have been dismounted.
Any ideas what could be wrong?
I have another machine with similar setup (secondary nameserver) and no problems there.
I've been trying to detect any configuration differences, but I found none.
2 hours of analysis and still no clues.
Any hints much appreciated.