seduction
 Language:
Welcome, Guest. Please login or register.
Did you miss your activation email?
2020/09/30, 08:59:24


Help

Author [EN] [PL] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: [solved] systemd issue -> found ordering cycle  (Read 2526 times)

0 Members and 1 Guest are viewing this topic.

Offline absolut

  • User
  • Posts: 437
[solved] systemd issue -> found ordering cycle
« on: 2020/06/11, 14:59:42 »
hi all!

a recent systemd update to 245.6-1 results during boot in following messages"

Code: [Select]
[    3.223373] systemd[1]: systemd 245.6-1 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
[    3.235055] systemd[1]: Detected architecture x86-64.
[    3.248415] systemd[1]: Set hostname to <sidbox>.
[    3.265743] systemd-fstab-generator[435]: x-systemd.device-timeout ignored for //192.168.178.3/homes/absolut
[    3.376337] systemd[1]: network-online.target: Found ordering cycle on network.target/start
[    3.376340] systemd[1]: network-online.target: Found dependency on networking.service/start
[    3.376341] systemd[1]: network-online.target: Found dependency on local-fs.target/start
[    3.376343] systemd[1]: network-online.target: Found dependency on media-nas_absolut.automount/start
[    3.376344] systemd[1]: network-online.target: Found dependency on network-online.target/start
[    3.376345] systemd[1]: network-online.target: Job network.target/start deleted to break ordering cycle starting with network-online.target/start
[    3.376675] systemd[1]: network-online.target: Found ordering cycle on networking.service/start
[    3.376677] systemd[1]: network-online.target: Found dependency on local-fs.target/start
[    3.376678] systemd[1]: network-online.target: Found dependency on media-nas_absolut.automount/start
[    3.376679] systemd[1]: network-online.target: Found dependency on network-online.target/start
[    3.376681] systemd[1]: network-online.target: Job networking.service/start deleted to break ordering cycle starting with network-online.target/start
[    3.376975] systemd[1]: sysinit.target: Found ordering cycle on haveged.service/start
[    3.376977] systemd[1]: sysinit.target: Found dependency on systemd-tmpfiles-setup.service/start
[    3.376978] systemd[1]: sysinit.target: Found dependency on local-fs.target/start
[    3.376979] systemd[1]: sysinit.target: Found dependency on media-nas_absolut.automount/start
[    3.376981] systemd[1]: sysinit.target: Found dependency on network-online.target/start
[    3.376982] systemd[1]: sysinit.target: Found dependency on NetworkManager-wait-online.service/start
[    3.376983] systemd[1]: sysinit.target: Found dependency on NetworkManager.service/start
[    3.376985] systemd[1]: sysinit.target: Found dependency on basic.target/start
[    3.376986] systemd[1]: sysinit.target: Found dependency on sockets.target/start
[    3.376987] systemd[1]: sysinit.target: Found dependency on pcscd.socket/start
[    3.376988] systemd[1]: sysinit.target: Found dependency on sysinit.target/start
[    3.376990] systemd[1]: sysinit.target: Job haveged.service/start deleted to break ordering cycle starting with sysinit.target/start
[    3.377291] systemd[1]: sysinit.target: Found ordering cycle on systemd-timesyncd.service/start
[    3.377292] systemd[1]: sysinit.target: Found dependency on systemd-tmpfiles-setup.service/start
[    3.377294] systemd[1]: sysinit.target: Found dependency on local-fs.target/start
[    3.377295] systemd[1]: sysinit.target: Found dependency on media-nas_absolut.automount/start
[    3.377296] systemd[1]: sysinit.target: Found dependency on network-online.target/start
[    3.377297] systemd[1]: sysinit.target: Found dependency on NetworkManager-wait-online.service/start
[    3.377299] systemd[1]: sysinit.target: Found dependency on NetworkManager.service/start
[    3.377300] systemd[1]: sysinit.target: Found dependency on basic.target/start
[    3.377301] systemd[1]: sysinit.target: Found dependency on sockets.target/start
[    3.377303] systemd[1]: sysinit.target: Found dependency on pcscd.socket/start
[    3.377304] systemd[1]: sysinit.target: Found dependency on sysinit.target/start
[    3.377305] systemd[1]: sysinit.target: Job systemd-timesyncd.service/start deleted to break ordering cycle starting with sysinit.target/start
[    3.377600] systemd[1]: sysinit.target: Found ordering cycle on systemd-update-utmp.service/verify-active
[    3.377602] systemd[1]: sysinit.target: Found dependency on systemd-tmpfiles-setup.service/start
[    3.377603] systemd[1]: sysinit.target: Found dependency on local-fs.target/start
[    3.377604] systemd[1]: sysinit.target: Found dependency on media-nas_absolut.automount/start
[    3.377605] systemd[1]: sysinit.target: Found dependency on network-online.target/start
[    3.377607] systemd[1]: sysinit.target: Found dependency on NetworkManager-wait-online.service/start
[    3.377608] systemd[1]: sysinit.target: Found dependency on NetworkManager.service/start
[    3.377609] systemd[1]: sysinit.target: Found dependency on basic.target/start
[    3.377610] systemd[1]: sysinit.target: Found dependency on sockets.target/start
[    3.377612] systemd[1]: sysinit.target: Found dependency on pcscd.socket/start
[    3.377613] systemd[1]: sysinit.target: Found dependency on sysinit.target/start
[    3.377614] systemd[1]: sysinit.target: Job systemd-update-utmp.service/verify-active deleted to break ordering cycle starting with sysinit.target/start
[    3.377909] systemd[1]: sysinit.target: Found ordering cycle on systemd-tmpfiles-setup.service/start
[    3.377910] systemd[1]: sysinit.target: Found dependency on local-fs.target/start
[    3.377911] systemd[1]: sysinit.target: Found dependency on media-nas_absolut.automount/start
[    3.377913] systemd[1]: sysinit.target: Found dependency on network-online.target/start
[    3.377914] systemd[1]: sysinit.target: Found dependency on NetworkManager-wait-online.service/start
[    3.377915] systemd[1]: sysinit.target: Found dependency on NetworkManager.service/start
[    3.377916] systemd[1]: sysinit.target: Found dependency on basic.target/start
[    3.377918] systemd[1]: sysinit.target: Found dependency on sockets.target/start
[    3.377919] systemd[1]: sysinit.target: Found dependency on pcscd.socket/start
[    3.377920] systemd[1]: sysinit.target: Found dependency on sysinit.target/start
[    3.377921] systemd[1]: sysinit.target: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with sysinit.target/start
[    3.378211] systemd[1]: sysinit.target: Found ordering cycle on systemd-machine-id-commit.service/start
[    3.378212] systemd[1]: sysinit.target: Found dependency on local-fs.target/start
[    3.378214] systemd[1]: sysinit.target: Found dependency on media-nas_absolut.automount/start
[    3.378215] systemd[1]: sysinit.target: Found dependency on network-online.target/start
[    3.378216] systemd[1]: sysinit.target: Found dependency on NetworkManager-wait-online.service/start
[    3.378217] systemd[1]: sysinit.target: Found dependency on NetworkManager.service/start
[    3.378219] systemd[1]: sysinit.target: Found dependency on basic.target/start
[    3.378220] systemd[1]: sysinit.target: Found dependency on sockets.target/start
[    3.378221] systemd[1]: sysinit.target: Found dependency on pcscd.socket/start
[    3.378222] systemd[1]: sysinit.target: Found dependency on sysinit.target/start
[    3.378224] systemd[1]: sysinit.target: Job systemd-machine-id-commit.service/start deleted to break ordering cycle starting with sysinit.target/start
[    3.378517] systemd[1]: sysinit.target: Found ordering cycle on apparmor.service/start
[    3.378518] systemd[1]: sysinit.target: Found dependency on local-fs.target/start
[    3.378519] systemd[1]: sysinit.target: Found dependency on media-nas_absolut.automount/start
[    3.378520] systemd[1]: sysinit.target: Found dependency on network-online.target/start
[    3.378522] systemd[1]: sysinit.target: Found dependency on NetworkManager-wait-online.service/start
[    3.378523] systemd[1]: sysinit.target: Found dependency on NetworkManager.service/start
[    3.378524] systemd[1]: sysinit.target: Found dependency on basic.target/start
[    3.378525] systemd[1]: sysinit.target: Found dependency on sockets.target/start
[    3.378527] systemd[1]: sysinit.target: Found dependency on pcscd.socket/start
[    3.378528] systemd[1]: sysinit.target: Found dependency on sysinit.target/start
[    3.378529] systemd[1]: sysinit.target: Job apparmor.service/start deleted to break ordering cycle starting with sysinit.target/start
[    3.378832] systemd[1]: sysinit.target: Found ordering cycle on local-fs.target/start
[    3.378833] systemd[1]: sysinit.target: Found dependency on media-nas_absolut.automount/start
[    3.378834] systemd[1]: sysinit.target: Found dependency on network-online.target/start
[    3.378836] systemd[1]: sysinit.target: Found dependency on NetworkManager-wait-online.service/start
[    3.378837] systemd[1]: sysinit.target: Found dependency on NetworkManager.service/start
[    3.378838] systemd[1]: sysinit.target: Found dependency on basic.target/start
[    3.378839] systemd[1]: sysinit.target: Found dependency on sockets.target/start
[    3.378841] systemd[1]: sysinit.target: Found dependency on pcscd.socket/start
[    3.378842] systemd[1]: sysinit.target: Found dependency on sysinit.target/start
[    3.378843] systemd[1]: sysinit.target: Job local-fs.target/start deleted to break ordering cycle starting with sysinit.target/start


i used this command to generate a graph (dot file) of the units:
Code: [Select]
systemd-analyze dot --no-pager --order > systemd_analyze_dot_file

then used this pythons script to search for cycles in dot files:
https://github.com/jantman/misc-scripts/blob/master/dot_find_cycles.py

the following output is generated, but i need a hand to interpret it... what does it tell me?
Code: [Select]
absolut@sidbox: ~ $ python3 dot_find_cycles.py systemd_analyze_dot_file --only-shortest

media-nas_absolut.automount -> network-online.target -> networking.service -> local-fs.target -> media-nas_absolut.automount
media-nas_absolut.automount -> network-online.target -> NetworkManager-wait-online.service -> sysinit.target -> local-fs.target -> media-nas_absolut.automount
systemd-networkd.service -> dns-clean.service -> local-fs.target -> media-nas_absolut.automount -> network-online.target -> network.target -> systemd-networkd.service
media-nas_absolut.automount -> network-online.target -> NetworkManager-wait-online.service -> NetworkManager.service -> dns-clean.service -> local-fs.target -> media-nas_absolut.automount
media-nas_absolut.automount -> network-online.target -> network.target -> NetworkManager.service -> dns-clean.service -> local-fs.target -> media-nas_absolut.automount
media-nas_absolut.automount -> network-online.target -> network.target -> NetworkManager.service -> sysinit.target -> local-fs.target -> media-nas_absolut.automount
media-nas_absolut.automount -> network-online.target -> network.target -> wpa_supplicant.service -> sysinit.target -> local-fs.target -> media-nas_absolut.automount
media-nas_absolut.automount -> network-online.target -> network.target -> network-pre.target -> resolvconf.service -> dns-clean.service -> local-fs.target -> media-nas_absolut.automount

the /ets/fstab file contains the entry:
Code: [Select]
//192.168.178.3/homes/absolut  /media/nas_absolut  cifs   vers=3.0,noauto,nofail,x-systemd.automount,x-systemd.requires=network-online.target,x-systemd.device-timeout=10,iocharset=utf8,user,uid=absolut,gid=users,rw,suid,noperm


help appreciated! thanks in advance!

best
absolut

« Last Edit: 2020/06/12, 21:41:34 by absolut »

Offline piper

  • Global Moderator
  • User
  • *****
  • Posts: 1.787
  • we are the priests ... of the temples of syrinx
Re: systemd issue -> found ordering cycle
« Reply #1 on: 2020/06/11, 17:32:26 »
Forgive me if I misunderstood, but this is a cosmetic issue, and a bug in debian. (a  longstanding bug in debian.)

Just an example

https://github.com/QubesOS/qubes-issues/issues/2193

You don't need qubes packages to see this :P


If this is not what your talking about, disregard what I said above and someone else might have a better answer or I am just babbling on with something I have no clue of.

 
Code: [Select]
journalctl -b | egrep "Found|Breaking"

Might help, might not
Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck

Offline absolut

  • User
  • Posts: 437
Re: systemd issue -> found ordering cycle
« Reply #2 on: 2020/06/11, 21:18:54 »
hi piper,
thanks for the input so far!

the cosmetic issue on my end actually is having a negative effect: the network manager target is deleted/killed to break the order cycle, thus i end up without network on my desktop.

i have for test purposes deactivated the /etc/fstab entry of my NAS mount, and the issue is gone!

now i need to figure out, how the hell on earth the fact of network mount generates a cycle...
any ideas?

Offline hendrikL

  • User
  • Posts: 429
Re: systemd issue -> found ordering cycle
« Reply #3 on: 2020/06/12, 08:35:57 »
And without that in the fstab line -->requires=network-online.target?
I don't have a NAS, but this req.......target seems to produce the cycle and i don't know if this entry is needed for automount!?


Offline absolut

  • User
  • Posts: 437
Re: systemd issue -> found ordering cycle
« Reply #4 on: 2020/06/12, 21:41:23 »
hi hendrikL!

i have been playing back and forth with fstab, and you are absolutely right... it turned out that removing the requires=network-online.target in the NAS mount options stops this faulty behavior. the option is not needed anymore (it was necessary back then, years ago).

thus, i consider the issue solved. for now.

thanks!
absolut

Offline piper

  • Global Moderator
  • User
  • *****
  • Posts: 1.787
  • we are the priests ... of the temples of syrinx
Re: [solved] systemd issue -> found ordering cycle
« Reply #5 on: 2020/06/14, 20:29:09 »
Glad you got it sorted!
Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck