http://bugzilla.opensuse.org/show_bug.cgi?id=1177491 http://bugzilla.opensuse.org/show_bug.cgi?id=1177491#c1 --- Comment #1 from Philippe Condé --- another example where time-sync.target is not started # systemctl status time-sync.target ● time-sync.target - System Time Synchronized Loaded: loaded (/usr/lib/systemd/system/time-sync.target; static) Active: inactive (dead) Docs: man:systemd.special(7) oct. 17 09:35:02 hpprol2 systemd[1]: named.service: Found ordering cycle on time-sync.target/start oct. 17 09:35:02 hpprol2 systemd[1]: named.service: Found dependency on ntpd.service/start oct. 17 09:35:02 hpprol2 systemd[1]: named.service: Found dependency on nss-lookup.target/start oct. 17 09:35:02 hpprol2 systemd[1]: named.service: Found dependency on named.service/start oct. 17 09:35:02 hpprol2 systemd[1]: named.service: Job time-sync.target/start deleted to break ordering cycle starting with named.service/start here again I cannot start it manually Regards Philippe -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177491 http://bugzilla.opensuse.org/show_bug.cgi?id=1177491#c3 Josef Möllers changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Assignee|max@suse.com |josef.moellers@suse.com --- Comment #3 from Josef Möllers --- As bind needs a (reasonably) accurate clock, replace the "time-sync.target" with "time-set.target". -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177491 http://bugzilla.opensuse.org/show_bug.cgi?id=1177491#c5 --- Comment #5 from Josef Möllers --- (In reply to Philippe Condé from comment #4)

Thanks this worked without error on ordering cycle

Great! Thanks for the feedback!

I have one more question:

Do I need changing the line "Wants=time-sync.target" to "Wants=time-set.target"?

Yes, please. Stay healthy! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177491 http://bugzilla.opensuse.org/show_bug.cgi?id=1177491#c9 --- Comment #9 from Philippe Condé --- (In reply to Karl Mistelberger from comment #8)

(In reply to Philippe Condé from comment #7)

...

If I understand correctly you suggest removing "Before=nss-lookup.target" ? Regards Philippe

Confirmed.

named.service has 3 requirements, which contradict each other:

After=network.target After=time-sync.target Before=nss-lookup.target

Dropping After=time-sync.target results in named starting before reliable time is available. Dropping Before=nss-lookup.target resolves the ordering problem. I guess After=network.target is covered by After=time-sync.target.

Ok, after reboot this morning I can confirm that after removing "Before=nss_lookup.target" there are no more error about ordering cycle and all other services are working. I suppose that this correction must be integrated in bind? Many thanks Philippe -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1177491 http://bugzilla.opensuse.org/show_bug.cgi?id=1177491#c11 Josef Möllers changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #11 from Josef Möllers --- First of all: Merci Philippe and Danke schön Karl for the analysis. IIUC the only change that is necessary is to remove the Before=nss-lookup.target Thanks and ... stay healthy! -- You are receiving this mail because: You are on the CC list for the bug.