`zerotier` Problems when the operation stops.

[zxlhhyccc]

Mon May 26 23:18:29 2025 daemon.err zerotier-one[13491]: WARNING: unable to write to file: /var/lib/zerotier-one/peers.d/ebe7fbd445.peer (unable to open)
Mon May 26 23:18:29 2025 daemon.err zerotier-one[13491]: WARNING: unable to write to file: /var/lib/zerotier-one/peers.d/b6079f73c6.peer (unable to open)
Mon May 26 23:18:29 2025 daemon.err zerotier-one[13491]: WARNING: unable to write to file: /var/lib/zerotier-one/peers.d/778cde7190.peer (unable to open)
Mon May 26 23:18:29 2025 daemon.err zerotier-one[13491]: WARNING: unable to write to file: /var/lib/zerotier-one/peers.d/cafefd6717.peer (unable to open)
Mon May 26 23:18:29 2025 daemon.err zerotier-one[13491]: WARNING: unable to write to file: /var/lib/zerotier-one/peers.d/cafe04eba9.peer (unable to open)
Mon May 26 23:18:29 2025 daemon.err zerotier-one[13491]: WARNING: unable to write to file: /var/lib/zerotier-one/peers.d/62f865ae71.peer (unable to open)
Mon May 26 23:18:29 2025 daemon.err zerotier-one[13491]: WARNING: unable to write to file: /var/lib/zerotier-one/peers.d/cafe80ed74.peer (unable to open)
Mon May 26 23:18:29 2025 daemon.err zerotier-one[13491]: WARNING: unable to write to file: /var/lib/zerotier-one/peers.d/cafe9efeb9.peer (unable to open)
Mon May 26 23:18:29 2025 daemon.err zerotier-one[13491]: Control Plane Stopped
Mon May 26 23:18:29 2025 daemon.err zerotier-one[13491]: V6 Control Plane Stopped
Mon May 26 23:18:29 2025 daemon.warn odhcpd[4345]: No default route present, setting ra_lifetime to 0!

[BKPepe]

Cc @mwarning

[mwarning]

How does your configuration look like?

[zxlhhyccc]

How does your configuration look like?

config zerotier 'global'
	option enabled '0'
	option port '9993'
	option secret '5cec1f48cf:0:a243b93a1e9b585860d07f078f6182595d3dea8a4ed4801d1055132f5fefa5683f801405633f9b1abf090b7fa75b9de014cdf161d62b62b47e420a48edaed898:84114f4f0f4c7120db0d549d133e32979e7d0fc7b6a497ce26c2502d81228fe4773d2c61413e7d24ac7a64ab3d95d373f2d6ef0250ac912457cdd0c503578e61'

config network 'earth'
	option id 'ebe7fbd445faf1ab'
	option allow_managed '1'
	option allow_global '0'
	option allow_default '1'
	option allow_dns '0'

[maovidal]

I'm experiencing the same errors:

Control Plane Stopped
V6 Control Plane Stopped

But I'm unable to see the warnings, so I'm not sure the cause would be the same.

However I must say that my Linux image and custom ZeroTier package is produced with Buildroot 2025.08.2. It is modified to remove SSO support to make it able to build (Reference here)

I've checked that TUN is running, and the working directory (and PID) file seems to be created without aparent issues.

Here is my configuration (With no networks joined yet). Sorry if I was over cautious redacting more than enough values here:

# zerotier-cli info -j
{
 "address": "<redacted>",
 "clock": <redacted>,
 "config": {
  "settings": {
   "allowTcpFallbackRelay": true,
   "forceTcpRelay": false,
   "homeDir": "/var/lib/zerotier-one",
   "listeningOn": [
    "192.168.19.102/9993",
    "192.168.19.103/9993",
    "192.168.19.102/32677",
    "192.168.19.103/32677",
    "192.168.19.102/40401",
    "192.168.19.103/40401"
   ],
   "portMappingEnabled": true,
   "primaryPort": 9993,
   "secondaryPort": 40401,
   "surfaceAddresses": [
    "<redacted>/3257",
    "<redacted>/50796",
    "<redacted>/2019"
   ],
   "tertiaryPort": 32677
  }
 },
 "online": true,
 "planetWorldId": <redacted>,
 "planetWorldTimestamp": <redacted>,
 "publicIdentity": "<redacted>,
 "tcpFallbackActive": false,
 "version": "1.16.0",
 "versionBuild": 0,
 "versionMajor": 1,
 "versionMinor": 16,
 "versionRev": 0
}

Joining a network is possible if done before the errors are announced. The web interface shows the device has joined. The configuration changes adding some addresses (related to the new ZT network) and changing the secondaryPort and tertiaryPort:

{
 "address": "<redacted>",
 "clock": <redacted>,
 "config": {
  "settings": {
   "allowTcpFallbackRelay": true,
   "forceTcpRelay": false,
   "homeDir": "/var/lib/zerotier-one",
   "listeningOn": [
    "192.168.19.102/9993",
    "192.168.19.103/9993",
    "192.168.19.102/65348",
    "192.168.19.103/65348",
    "192.168.19.102/22190",
    "192.168.19.103/22190"
   ],
   "portMappingEnabled": true,
   "primaryPort": 9993,
   "secondaryPort": 65348,
   "surfaceAddresses": [
    "192.168.19.103/22190",
    "192.168.19.102/22190",
    "192.168.19.103/65348",
    "192.168.19.102/65348",
    "192.168.19.103/9993",
    "192.168.19.102/9993",
    "<redacted>/2019",
    "<redacted>/3257",
    "<redacted>/22190",
    "<redacted>/62367",
    "<redacted>/65348",
    "<redacted>/46952"
   ],
   "tertiaryPort": 22190
  }
 },
 "online": true,
 "planetWorldId": <redacted>,
 "planetWorldTimestamp": <redacted>,
 "publicIdentity": "<redacted>,
 "tcpFallbackActive": false,
 "version": "1.16.0",
 "versionBuild": 0,
 "versionMajor": 1,
 "versionMinor": 16,
 "versionRev": 0
}

Any help, would be greatly appreciated.

[maovidal]

I'm so sorry about my previous post. I just noticed this repo is for openwrt, not the zerotier-one repo. If that is okay I would leave it here anyway, as in both cases the packages are being custom built.

[maovidal]

Again, I’m sorry. My issue had nothing to do with ZeroTier itself.

The problem was in its monitoring: I incorrectly configured Monit with the wrong PID file location. ZeroTier stores its PID file in its working directory rather than the usual /var/run.