[opensuse-factory] systemd ordering cycles affecting systemd-fsck-root.service?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 After updating my experimental openSUSE Tumbleweed server to the latest snapshot, I experienced an unexpected technical issue that caused networking to randomly fail. After having stumbled upon the solution on the mailing list archives (http://lists.opensuse.org/opensuse-factory/2015-10/msg00243.html), I rebooted the server and continued to experience some systemd ordering cycle issues. Relevant dmesg output:
[ 1.797448] systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped [ 1.835699] systemd[1]: systemd-readahead-collect.service: Cannot add dependency job, ignoring: Unit systemd-readahead-collect.service failed to load: No such file or directory. [ 1.838411] systemd[1]: systemd-readahead-replay.service: Cannot add dependency job, ignoring: Unit systemd-readahead-replay.service failed to load: No such file or directory. [ 1.841274] systemd[1]: systemd-fsck-root.service: Found ordering cycle on systemd-fsck-root.service/start [ 1.842965] systemd[1]: systemd-fsck-root.service: Found dependency on systemd-journald.socket/start [ 1.844430] systemd[1]: systemd-fsck-root.service: Found dependency on haveged.service/start [ 1.845664] systemd[1]: systemd-fsck-root.service: Found dependency on systemd-random-seed.service/start [ 1.847163] systemd[1]: systemd-fsck-root.service: Found dependency on systemd-remount-fs.service/start [ 1.848607] systemd[1]: systemd-fsck-root.service: Found dependency on systemd-fsck-root.service/start [ 1.850116] systemd[1]: systemd-fsck-root.service: Breaking ordering cycle by deleting job systemd-journald.socket/start [ 1.851787] systemd[1]: systemd-journald.socket: Job systemd-journald.socket/start deleted to break ordering cycle starting with systemd-fsck-root.service/start
Is there still an issue with the way systemd or its units are configured? I'm a noob at systemd, so I might need some pointers to understand what's going on here. For clarity, it's a Linode VPS on a paravirtualized KVM hypervisor using their most current kernel (4.1.5-x86_64-linode61), but I doubt the kernel is the issue here as both my production server (openSUSE 13.2) and the experimental server prior to the upgrade were running properly with this kernel. Any idea what might be wrong here? - -- Brian "DragonLord" Wong http://www.fierydragonlord.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWHyTrAAoJEEUv29mnaAr0RI0QALWHHZ1sa/iSXujH17pHME8S 8gRtdvANsFSv3mTldAMhNwTYsL8pFj8kNcAitXzLN2dH97/eO6+gqjh0MtO/b1zD w5C22J25n8LT3Afwy3xyBR9cdfHIq31H1o0nK9Ut1Uzgno9+/zovA514tirBQDeC D0w5wlkBNIKnGeANbvkbt+NSiE3wep1iAKSH1sNQ+pREyxrI9hcGorPfrSBptkcI UAm8NZ5BwA/L1cN8xBeZDA/J90QNuniLTitI04AF79bmnmnwql2jLUgMLFj+kxMW iVke4/XmFNKVnQhaPXibEukJonCRQe7EcPziyqDyu2WlyTLGQNXVW9Apr7OzRaBE UOIgBxFWJyz6sEgWLcL/XFuZ7MhvPo+Xa8nC1yjdJ7LBJPevU01OO3iMaxhNx75B 53seVZyMFARvASrvVbfPWadMoK5gXaMA8yCMTMIZulFyqVbjWg5nXfU7xbrNH77G dv84GeMl40ZH47aRZmkqCTZ3CKpUjKMQdqawwVsmxmaBeyvbjGhQ1S39JosX96i1 QXbJFIVs7c6xB4AIqKLd8rryHsXbGzwJSeM8vyYifJ7qoBZxB1hOvs8KtcPrx0h6 pvGaAx2C6tR7pW/yQsBJIwwdNFUVcuo2TyEkWVCtOTzW7gUHgwI1MKxHx3FZZ3+I jlDhS+DzC3FZYmYVckQW =l/3g -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (1)
-
Brian "DragonLord" Wong