You are not logged in.
I've installed ZeroTier on my Arch Linux box. I'm seeing that it takes 2 whole minutes to start up:
# time systemctl start zerotier-one.service
real 2m0.208s
user 0m0.015s
sys 0m0.007s
I've checked:
$ systemd-analyze blame
2min 165ms systemd-networkd-wait-online.service
...
and:
# journalctl -b -u systemd-networkd-wait-online
Aug 04 17:13:54 hostname systemd[1]: Starting Wait for Network to be Configured...
Aug 04 17:15:54 hostname systemd-networkd-wait-online[748]: Timeout occurred while waiting for network connectivity.
Aug 04 17:15:54 hostname systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
Aug 04 17:15:54 hostname systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
Aug 04 17:15:54 hostname systemd[1]: Failed to start Wait for Network to be Configured.
# journalctl -b -u zerotier-one
Aug 04 17:15:54 hostname systemd[1]: Started ZeroTier One.
Aug 04 17:15:55 hostname zerotier-one[829]: Starting Control Plane...
Aug 04 17:15:55 hostname zerotier-one[829]: Starting V6 Control Plane...
So those 2 whole minutes are really being used by systemd-networkd-wait-online and not by ZeroTier, I believe.
What really is happening? Would appreciate any help. Thanks!
Last edited by codeandfire (2024-08-04 12:37:39)
Offline
This related question mentions that if you aren't using systemd-networkd to manage your network configuration, you should probably disable its two services:
# systemctl disable systemd-networkd.service systemd-networkd-wait-online.service
I've been using IWD on my laptop to manage networks, so I disabled them and voila ZeroTier starts up in 0.02 seconds now.
Surprising I never noticed this - but it solves the issue.
Offline