`zerotier` Problems when the operation stops.
Open
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
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!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported zerotier-one and odhcpd log output, then reproduce the operation stop and inspect the package behavior around the peer-file write failures and control-plane shutdown. The issue names no source files, tests, or expected behavior, so a complete fix would first require identifying the failure cause and defining a verifiable recovery result.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100