I am getting the same problem here, but using the open-iscsi initiator (which - of course - depends on the network being initialized):
Found ordering cycle on sysinit.target/start [ 3.657825] systemd[1]: Found dependency on open-iscsi.service/start [ 3.657827] systemd[1]: Found dependency on network-online.target/start [ 3.657828] systemd[1]: Found dependency on NetworkManager-wait-online.service/start [ 3.657830] systemd[1]: Found dependency on basic.target/start [ 3.657831] systemd[1]: Found dependency on sockets.target/start [ 3.657833] systemd[1]: Found dependency on acpid.socket/start [ 3.657834] systemd[1]: Found dependency on sysinit.target/start [ 3.657836] systemd[1]: Breaking ordering cycle by deleting job open-iscsi.service/start [ 3.657837] systemd[1]: Job open-iscsi.service/start deleted to break ordering cycle starting with sysinit.target/start So, it is quite a systematic problem with the System-V init scripts and their dependency setup in systemd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452644 Title: vivid NFSd does not start due to systemd ordering cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1452644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
