Since the 20151012 snapshot I’m seeing this during system boot:
haveged.service: Job haveged.service/start deleted to break ordering cycle starting with systemd-journald.socket/start
The ‘full’ message from the log is:
3.385772] systemd[1]: systemd-journald.socket: Found ordering cycle on systemd-journald.socket/start
3.385780] systemd[1]: systemd-journald.socket: Found dependency on haveged.service/start
3.385784] systemd[1]: systemd-journald.socket: Found dependency on systemd-journald.socket/start
3.385787] systemd[1]: systemd-journald.socket: Breaking ordering cycle by deleting job haveged.service/start
3.385791] systemd[1]: haveged.service: Job haveged.service/start deleted to break ordering cycle starting with systemd-journald.socket/start
Now, my knowledge of systemd could be written legibly on the head of a pin…
A quick Google around didn’t yield anything useful.
As journald seems to feature in this, and I’m using rsyslog, a wild stab in the dark was to temporarily remove rsyslog… which made absolutely no difference.
Hints, pointers, or other ideas welcome :\
You probably show incomplete log. I have TW and haveged and no cycles. Something else is probably there that is not shown.
OK… but I don’t immediately see anything obvious, at least to me.
paul@Orion-Tumble:~$ dmesg | grep -i systemd
3.323154] random: systemd urandom read with 23 bits of entropy available
3.324085] systemd[1]: systemd 224 running in system mode. (+PAM +AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD +IDN)
3.324275] systemd[1]: Detected architecture x86-64.
3.324278] systemd[1]: Running in initial RAM disk.
3.324306] systemd[1]: Set hostname to <Orion-Tumble>.
3.328468] systemd-fstab-generator[86]: Failed to create mount unit file /run/systemd/generator/sysroot.mount, as it already exists. Duplicate entry in /etc/fstab?
3.329237] systemd[83]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with error code 1.
3.377028] systemd[1]: systemd-journald.socket: Found ordering cycle on systemd-journald.socket/start
3.377036] systemd[1]: systemd-journald.socket: Found dependency on haveged.service/start
3.377039] systemd[1]: systemd-journald.socket: Found dependency on systemd-journald.socket/start
3.377043] systemd[1]: systemd-journald.socket: Breaking ordering cycle by deleting job haveged.service/start
3.377047] systemd[1]: haveged.service: Job haveged.service/start deleted to break ordering cycle starting with systemd-journald.socket/start
3.377763] systemd[1]: Reached target Swap.
This is all systemd related from dmesg on a fresh boot prior to the line:
“… haveged.service: Job haveged.service/start deleted to break ordering cycle …”
Entire output of dmesg http://paste.opensuse.org/2fd3522d
haveged is in essence a random number generator. Not running it may make any random number the system uses a bit more predictable
Ah, OK, so this happens in initrd. I see it with latest TW indeed. Not sure right now what is the reason. But bug report is definitely in order (sorry, pun unintended).