Bugzilla – Bug 965475
openSUSE:13.1:Update/systemd: Bug "Found ordering cycle on fix.service/start"
Last modified: 2016-03-18 13:19:06 UTC
after an update of systemd from 208 to 210 postfix doesn't start anymore via systemd on boot cause of a "Found ordering cycle on fix.service/start". ntp (and probably other sysv based services) is also affected. a manual start via systemctl start postfix.service systemctl start ntp.service works as expected. journalctl says: systemd[1]: Found ordering cycle on fix.service/start systemd[1]: Found dependency on nss-lookup.target/start systemd[1]: Found dependency on named.service/start systemd[1]: Found dependency on remote-fs.target/start systemd[1]: Found dependency on fix.service/start systemd[1]: Breaking ordering cycle by deleting job nss-lookup.target/start systemd[1]: Job nss-lookup.target/start deleted to break ordering cycle starting with fix.service/start systemd[1]: Deleting job ntp.service/start as dependency of job nss-lookup.target/start systemd[1]: Deleting job postfix.service/start as dependency of job nss-lookup.target/start additional infos: systemctl is-enabled postfix.service enabled systemctl is-enabled ntp.service enabled systemctl status postfix.service postfix.service - Postfix Mail Transport Agent Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled) Active: inactive (dead) systemctl status ntp.service ntp.service - LSB: Network time protocol daemon (ntpd) Loaded: loaded (/etc/init.d/ntp) Drop-In: /run/systemd/generator/ntp.service.d └─50-insserv.conf-$time.conf Active: inactive (dead) "nss-lookup.target" is included in postfix.service via Requires=var-run.mount nss-lookup.target network.target remote-fs.target time-sync.target and is also injected from systemd for sysv based services (/etc/init.d/) like ntp
more tests/infos: if named is disabled systemctl disable named.service systemctl is-enabled named.service disabled postfix and ntp are working well on boot, so the problem seems to be related to an active named.service ?
I've found this posts https://bugzilla.suse.com/show_bug.cgi?id=905639#c51 https://bugzilla.suse.com/show_bug.cgi?id=905639#c52 after removing "nss-lookup.target" from "After=" in /usr/lib/systemd/system/fix.service postfix+ntp+named start properly on boot. don't know if this has other impacts, but for now this works for me.
(In reply to Paolo Panto from comment #2) > I've found this posts > https://bugzilla.suse.com/show_bug.cgi?id=905639#c51 > https://bugzilla.suse.com/show_bug.cgi?id=905639#c52 > > after removing "nss-lookup.target" from "After=" in > /usr/lib/systemd/system/fix.service > postfix+ntp+named start properly on boot. > > don't know if this has other impacts, but for now this works for me. fix.service seems not needed anymore. Could you try to remove it completely instead ? Try something like: rm /usr/lib/systemd/system/remote-fs.target.wants/fix.service rm /usr/lib/systemd/system/fix.service Thanks.
(In reply to Franck Bui from comment #3) > (In reply to Paolo Panto from comment #2) > > I've found this posts > > https://bugzilla.suse.com/show_bug.cgi?id=905639#c51 > > https://bugzilla.suse.com/show_bug.cgi?id=905639#c52 > > > > after removing "nss-lookup.target" from "After=" in > > /usr/lib/systemd/system/fix.service > > postfix+ntp+named start properly on boot. > > > > don't know if this has other impacts, but for now this works for me. > > fix.service seems not needed anymore. Could you try to remove it completely > instead ? > > Try something like: > > rm /usr/lib/systemd/system/remote-fs.target.wants/fix.service > rm /usr/lib/systemd/system/fix.service > > Thanks. files removed on two systems for testing and both reboot without problems. fix.service was probably added (such as the content suggests) to avoid shutdown problems with autofs and nfs services? I've tested this with a mounted cifs-mount via autofs and it seems to work properly after removing fix.service (nfs not tested). thanks for the help.
(In reply to Paolo Panto from comment #4) > > fix.service was probably added (such as the content suggests) to avoid > shutdown problems with autofs and nfs services? yes indeed and it was only needed by v208. > > I've tested this with a mounted cifs-mount via autofs and it seems to > work properly after removing fix.service (nfs not tested). > Thanks for testing. fix.service will be removed from the next package update.
Franck, could this be added to (or actually removed from) the running maintenance update for 13.1? https://build.opensuse.org/project/show/openSUSE:Evergreen:Maintenance:395
(In reply to Wolfgang Rosenauer from comment #7) > Franck, could this be added to (or actually removed from) the running > maintenance update for 13.1? > https://build.opensuse.org/project/show/openSUSE:Evergreen:Maintenance:395 I've submitted the latest pending changes for 13.1: https://build.opensuse.org/request/show/358824 This includes the removal of fix.service.
What is the status here? The mentioned update did not arrive in the regular update repository, as far as I can see. I have persistent problems with part of my machines running a combination of networkmanager and NFS mounts, where several things, including postfix and the X server, don't start due to dependency issues around remote-fs.target. And I'd love to also update these systems eventually, now the glibc fix is there...
You can help testing: Subscribe to http://download.opensuse.org/repositories/openSUSE:/Evergreen:/Maintenance:/401/openSUSE_13.1_Update/ and report your findings.
(In reply to Wolfgang Rosenauer from comment #10) > You can help testing: > Subscribe to > http://download.opensuse.org/repositories/openSUSE:/Evergreen:/Maintenance:/ > 401/openSUSE_13.1_Update/ > and report your findings. Thanks! Doesn't help with my laptop issues, unfortunately :( Boot shows me these: 2016-02-19T12:33:51.118742+01:00 lat17 systemd[1]: Dependency failed for Remote File Systems. 2016-02-19T12:33:51.119001+01:00 lat17 systemd[1]: Dependency failed for Postfix Mail Transport Agent. 2016-02-19T12:33:51.119239+01:00 lat17 systemd[1]: Dependency failed for LSB: X Display Manager. 2016-02-19T12:33:51.119551+01:00 lat17 systemd[1]: Dependency failed for LSB: Network time protocol daemon (ntpd). The stuff starts when I "systemctl start" it by hand. Anything specific I can do / report now?
This is an autogenerated message for OBS integration: This bug (965475) was mentioned in https://build.opensuse.org/request/show/360895 13.1 / systemd
(In reply to Patrick Schaaf from comment #11) > (In reply to Wolfgang Rosenauer from comment #10) > > You can help testing: > > Subscribe to > > http://download.opensuse.org/repositories/openSUSE:/Evergreen:/Maintenance:/ > > 401/openSUSE_13.1_Update/ > > and report your findings. > > Thanks! > > Doesn't help with my laptop issues, unfortunately :( > Are you laptop issues also involve "fix.service" unit ? Did they appear after upgrading systemd from 208 to 210 ? From your comment #9, it's not clear to me.
(In reply to Franck Bui from comment #13) > > Doesn't help with my laptop issues, unfortunately :( > > > Are you laptop issues also involve "fix.service" unit ? I don't know. At least it did not help to simply remove that fix.service. I tried that. Probably not - I don't think I saw the "Found ordering cycle" message there. > Did they appear after upgrading systemd from 208 to 210 ? Yes. I can try reverting to 208 on that laptop, tomorrow. (it's remote without anybody near at the moment, and after downgrade from 210 to 208 shutdown does not work, unfortunately....) If there is anything that I could usefully run and save the output of, comparing the situation on the laptop before and after the 210->208 downgrade attempt?
(In reply to Patrick Schaaf from comment #14) > (In reply to Franck Bui from comment #13) > > > Doesn't help with my laptop issues, unfortunately :( > > > > > > Are you laptop issues also involve "fix.service" unit ? > > I don't know. At least it did not help to simply remove that fix.service. I > tried that. > That sounds like another bug IMO. > Probably not - I don't think I saw the "Found ordering cycle" message there. > > > Did they appear after upgrading systemd from 208 to 210 ? > > Yes. > > I can try reverting to 208 on that laptop, tomorrow. (it's remote without > anybody near at the moment, and after downgrade from 210 to 208 shutdown > does not work, unfortunately....) > > If there is anything that I could usefully run and save the output of, > comparing the situation on the laptop before and after the 210->208 > downgrade attempt? Well if you cannot easily switch back to 208 that doesn't really matter, this info could have been useful but we can live without it. I would suggest to create a new bug (since removing fix.service is not enough) and attach the output of 'journalctl -b'. Before doing that, make sure to reboot and add to the kernel command line 'systemd.log_level=debug' and also remove 'quiet' from it. Thanks.
This is an autogenerated message for OBS integration: This bug (965475) was mentioned in https://build.opensuse.org/request/show/361237 13.2 / systemd
(In reply to Franck Bui from comment #15) > I would suggest to create a new bug (since removing fix.service is not > enough) and attach the output of 'journalctl -b'. DONE: https://bugzilla.opensuse.org/show_bug.cgi?id=968042
SUSE-RU-2016:0586-1: An update that has 17 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 927250,942946,948458,948555,949574,954336,954781,955469,955770,958295,958935,958937,961226,961576,962080,964355,965475 CVE References: Sources used: SUSE Linux Enterprise Software Development Kit 12-SP1 (src): systemd-210-95.1 SUSE Linux Enterprise Server 12-SP1 (src): systemd-210-95.1 SUSE Linux Enterprise Desktop 12-SP1 (src): systemd-210-95.1
SUSE-RU-2016:0587-1: An update that has 15 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 927250,942946,948458,948555,949574,955469,955770,958295,958935,958937,961226,961576,962080,964355,965475 CVE References: Sources used: SUSE Linux Enterprise Software Development Kit 12 (src): systemd-210-70.39.1 SUSE Linux Enterprise Server 12 (src): systemd-210-70.39.1 SUSE Linux Enterprise Desktop 12 (src): systemd-210-70.39.1
openSUSE-RU-2016:0691-1: An update that has 10 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 942946,955469,955770,958295,958935,958937,961226,962080,964355,965475 CVE References: Sources used: openSUSE 13.1 (src): systemd-210-43.1, systemd-mini-210-43.2
This should be fixed by the latest update of systemd. Feel free to reopen if it's not the case.
after updating systemd from 210-40.1 to 210-43.1 its looking good :-) thanks!
openSUSE-RU-2016:0815-1: An update that has 17 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 927250,942946,948458,948555,949574,954336,954781,955469,955770,958295,958935,958937,961226,961576,962080,964355,965475 CVE References: Sources used: openSUSE Leap 42.1 (src): systemd-210-89.1, systemd-mini-210-89.1