Fails to connect on boot

[UndarkAido]

I get this from ZeroTier on boot:

$ sudo service zerotier-one status
● zerotier-one.service - ZeroTier One
   Loaded: loaded (/lib/systemd/system/zerotier-one.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2018-04-29 00:19:04 CDT; 5min ago
 Main PID: 801 (zerotier-one)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/zerotier-one.service
           └─801 /usr/sbin/zerotier-one

Apr 29 00:19:04 Yamato systemd[1]: Started ZeroTier One.
Apr 29 00:19:04 Yamato zerotier-one[801]: sendto: Network unreachable

Running zerotier-cli with sudo or restarting the service make it work. Anyone know what's up?

[adamierymenko]

Does it work if you wait or do you have to restart? A network unreachable error may not be fatal since it keeps trying.

[UndarkAido]

It doesn't work until I manually interact with it by restarting or running it with `sudo` from the command line.

…

On Mon, May 7, 2018, 1:46 PM Adam Ierymenko ***@***.***> wrote: Does it work if you wait or do you have to restart? A network unreachable error may not be fatal since it keeps trying. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#728 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHE_YvmfKcS9o7T88bLKN-Eupj3QOLHQks5twJZogaJpZM4TrrND> .

[adamierymenko]

Can you tell me a little more about the system? Hardware, OS/distribution, etc.?

[UndarkAido]

It's a Dell Optiplex with an i7, Ubuntu 17.10.

…

On Mon, May 7, 2018, 2:59 PM Adam Ierymenko ***@***.***> wrote: Can you tell me a little more about the system? Hardware, OS/distribution, etc.? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#728 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHE_Ygl3WvSSji2zj9o9fxZQpxSRJr5Nks5twKeKgaJpZM4TrrND> .

[richarke]

I have the same issue on Raspbian (Stretch) with zt 1.2.8. Seems to be some kind of systemd race. I added this to the [Service] section of /lib/systemd/system/zerotier-one:

ExecStartPre=/bin/sleep 10

It fixes the problem for me. (There's probably a better way...)

[norn93]

I tried @richarke's solution:

ExecStartPre=/bin/sleep 10

but it didn't work for me.

I fixed the same issue by adding the sleep in /etc/rc.local:

sleep 60
sudo systemctl restart zerotier-one

Very hacky, but hasn't given me any problems yet. The issue arose because I'm using a weird 3G/4G USB dongle as eth1.

[laduke]

There were some changes to the systemd units in the last couple releases.
Feel free to re-open if needed.

[AurevoirXavier]

Still got this problem in 2020.

Every 5 minutes it'll restart but still got sendto: Network unreachable.

It doesn't work until I manually interact with it by restarting or running it with sudo from the command line.

I'm on Arch Linux with latest update.

[laduke]

Is it version 1.5? https://bugs.archlinux.org/task/68177?project=5&string=zerotier-one

[AurevoirXavier]

Is it version 1.5? https://bugs.archlinux.org/task/68177?project=5&string=zerotier-one

Yes