On Wed, Apr 18, 2018 at 5:13 AM, Daniel Stirnimann <daniel.stirnim...@switch.ch> wrote: > On 18.04.18 10:57, Blason R wrote: >> Well it just loads fine when I run from command line i.e. named -u named >> -n 4 -c /etc/named.conf >
... and how long does it take to start up when doing so (in case it is simply taking too long and systemd get bored waiting). Also, what does: systemctl status -l -n 50 named and journalctl -u named show? Gah, I hate systemd - it makes debugging startup really hard. W > Just a guess. If you use and have SELinux in enforcing mode (see > getenforce), this could be a reason. Your user process runs unconfined > that's why it works from the command line if you have a policy violation. > > You may want to check the audit logs and fix the broken configuration. > > sealert -a /var/log/audit/audit.log > > > Daniel > _______________________________________________ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe > from this list > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
