zerotier / zerotier/ZeroTierOne

Unable to Start Zervice on Debian 12

Open
#2,272 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
17.1k
Forks
2k
PR merge metrics
No merged PRs in 30d

Description

I installed zerotier on a fresh install of Debian using the install script:
curl -s https://install.zerotier.com | sudo bash

After install, the following error message appears:

*** Enabling and starting ZeroTier service...
Synchronizing state of zerotier-one.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable zerotier-one
Job for zerotier-one.service failed because the control process exited with error code.
See "systemctl status zerotier-one.service" and "journalctl -xeu zerotier-one.service" for details.

*** Package installed but cannot start service! You may be in a Docker
*** container or using a non-standard init service.

and I am unable to run zerotier via the commandline.
sudo systemctl status zerotier-one.service returns the following:

× zerotier-one.service - ZeroTier One
     Loaded: loaded (/usr/lib/systemd/system/zerotier-one.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Fri 2024-04-12 09:44:39 JST; 5min ago
   Duration: 1ms
   Main PID: 31836 (code=exited, status=127)
        CPU: 824us

Apr 12 09:44:39 mogura systemd[1]: zerotier-one.service: Scheduled restart job, restart counter is at 5.
Apr 12 09:44:39 mogura systemd[1]: zerotier-one.service: Start request repeated too quickly.
Apr 12 09:44:39 mogura systemd[1]: zerotier-one.service: Failed with result 'exit-code'.
Apr 12 09:44:39 mogura systemd[1]: Failed to start zerotier-one.service - ZeroTier One.

I've tried reinstalling several times, but it always comes up the same way.
What could I be missing here?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Debian 12 installation with the documented curl command, then run the mentioned systemctl status and journalctl commands to identify why zerotier-one exits with status 127. Inspect the installation script and zerotier-one service setup for Debian-specific assumptions; done means the service starts successfully and ZeroTier can be run from the command line.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, debian, linux
Domain
networking, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.