Hello,
I noticed that named was not started when I reboot my system.
My system start wicked, ntpd, dhcpd , pppd and named servers
I find this status error
# systemctl status named
● named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
Active: inactive (dead)
Jul 02 08:13:40 hpprol2 systemd[1]: nss-lookup.target: Found ordering cycle on named.service/start
Jul 02 08:13:40 hpprol2 systemd[1]: nss-lookup.target: Found dependency on time-sync.target/start
Jul 02 08:13:40 hpprol2 systemd[1]: nss-lookup.target: Found dependency on ntpd.service/start
Jul 02 08:13:40 hpprol2 systemd[1]: nss-lookup.target: Found dependency on nss-lookup.target/start
Jul 02 08:13:40 hpprol2 systemd[1]: nss-lookup.target: Job named.service/start deleted to break ordering cycle starting with nss-lookup.target/start
If I look in journalctl I see that these messages occur very early (just after the start of journal) before the start of wicked, pppd and ntpd.
There is also none other messages about nss-lookup.
Can it be due to an analyze of some systemd scripts?
One thing that I find strange is that this error doesn’t occurs if I do a reboot after installing a new kernel (and also a purge of old kernel)
Any idea where to look?
Should I open a bug report?
Many thanks in advance
Philippe