Mailinglist Archive: opensuse-factory (1324 mails)

< Previous Next >
[opensuse-factory] systemd ordering cycles affecting systemd-fsck-root.service?
  • From: "Brian \"DragonLord\" Wong" <draconicpenguin1@xxxxxxxxx>
  • Date: Thu, 15 Oct 2015 00:03:18 -0400
  • Message-id: <561F2586.1030004@yahoo.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Sorry if I sent this twice, Enigmail might have messed up the signature.

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

iQIcBAEBCAAGBQJWHyWGAAoJEEUv29mnaAr0yasQAKuCxdTP4fWdVCMu8c/+SUq4
xo/AXf56ALrmnwqjjQcg0i+lFn5pvmdUkq7kzDuWnde3aLwhdG4F/5zkdEYIzOy5
UlVLUlGcBfQlBT3lFkx5S2B5yHJJUcr7U9DWkJ2cdM+7/ndjHCisK8d8VNNCi2Hk
xsfdHl+BWZWCHvQy2lwq19kJV0waeRdcungt8VfaYZiQazc0AS1vdNdKaEymfzr5
2iJKShUy1yJlghLISQPy68vroHw3LudFOPtUMdgbEuRT8S2p2tZcudTfMgWU4CEt
inJ7w5yzgwYQlOMeQAd+9pMAAd+qoVh5YTLPbDpd4awQmjUC5Dcdtb9i9Cy9Ma/r
8eqVLoWoNhV+nDXnRWmZMqpmjAwJ4HYC8x7lY+y36/FDWKv1kjfmy7msq6TzpxDf
UJbt4RYNiLxeh21d/fWXwYt8Nc7LA5u7H7oKp7frG+6xB8VNquFVAxgMHCwjFPQO
TUDoxxgmSEbeGeuqGuD2TbNqUoWDBrwrWiQDSjxPpStyKe473b++KsMutWGvlRrX
t7uHytdR1kO2x99BESpv+RARwQsRhJf+bUTyeFeyKHs3m1Uvdct0fBeTLWZFfuqZ
euxPu6gfnZG8Xx5cVVydtgqgz/5S6kpvHSuFjVeYph964M5fptp2jMKp+zB0izjw
pLjGYmMhvHTVON1/q8cS
=XWyq
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >