The used systemd service file leads to the following logged message: # unifi.service: Job network-online.target/start deleted to break ordering cycle starting with unifi.service/start Reproducible: Always
Does the message disappear, if you do remove 'After=network-online.target' from unit?
I don't think that network.target is the right target to specify in WantedBy. According to [1], the network.target indicates when the network functionality is available, so I think only providers of the network connection (e.g. netifrc, NetworkManager) should somehow provide network.target. Also, network-online.target indicates that the network is already online, which can't be the case for services starting in network.target as they are the ones that need to do the work to reach network-online.target. When wanting a network when starting the application, one should rather use Wants=network.target and After=network.target. And since this daemon probably doesn't provide network connectivity, it should rather be WantedBy=multi-user.target or WantedBy=default.target. Swithing to multi-user.target or default.target is probably the right solution for this problem. [1] https://www.freedesktop.org/software/systemd/man/systemd.special.html
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=372e0e11f3768b2f50eb844f5ae430498bc73fc5 commit 372e0e11f3768b2f50eb844f5ae430498bc73fc5 Author: Conrad Kostecki <conikost@gentoo.org> AuthorDate: 2022-04-13 13:39:39 +0000 Commit: Conrad Kostecki <conikost@gentoo.org> CommitDate: 2022-04-13 13:39:39 +0000 net-wireless/unifi: fix systemd unit Closes: https://bugs.gentoo.org/837908 Signed-off-by: Conrad Kostecki <conikost@gentoo.org> net-wireless/unifi/files/{unifi.service-r1 => unifi.service-r2} | 4 ++-- net-wireless/unifi/{unifi-6.5.55-r1.ebuild => unifi-6.5.55-r2.ebuild} | 2 +- net-wireless/unifi/{unifi-7.0.25-r1.ebuild => unifi-7.0.25-r2.ebuild} | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-)
Thank you!
