SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-06-11 18:02:48 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

systemd unit file improvements #418

New Issue
Open
opened 2025-11-20 05:11:05 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 05:11:05 -05:00
Owner
Copy Link

Originally created by @sebastianschauenburg on GitHub (Aug 12, 2023).

Describe the problem
After a reboot, netbird fails to start using the systemd unit file netbird.service. Example of an error which is visible:

aug 11 12:48:14 hostname systemd[7480]: netbird.service: Failed to set up standard output: No such file or directory

I'm using a Ubuntu 23.04 system with netbird 0.22.3 (installed via apt).

To Reproduce

  1. Set up /var/log as RAM log with (for example) log2ram.
  2. Reboot the system
  3. View the error logs

Expected behavior
No errors and a working netbird interface

Additional context

/var/log/netbird is created at a certain point, but was not synced to the persistent /var/log (if available). So effectively, after a reboot, the /var/log/netbird directory does not exist. This in turn means it cannot be used for stdout and stderr.
I tried creating it with an ExecStartPre using mkdir inside the unit file, but attaching the stdout and stderr apparently happens before that point and as such, errors with:

aug 11 12:49:36 hostname systemd[8997]: netbird.service: Failed at step STDOUT spawning /usr/bin/mkdir: No such file or directory

Proposed solution
Add this to the unit file, which ensures client.log can be created / updated:

ExecStartPre=/usr/bin/mkdir /var/log/netbird

Remove the following lines, since that output should be captured inside of systemd (journalctl) anyway:

StandardOutput=file:/var/log/netbird/netbird.out
StandardError=file:/var/log/netbird/netbird.err
Originally created by @sebastianschauenburg on GitHub (Aug 12, 2023). **Describe the problem** After a reboot, netbird fails to start using the systemd unit file ```netbird.service```. Example of an error which is visible: aug 11 12:48:14 hostname systemd[7480]: netbird.service: Failed to set up standard output: No such file or directory I'm using a Ubuntu 23.04 system with netbird 0.22.3 (installed via apt). **To Reproduce** 1. Set up /var/log as RAM log with (for example) [log2ram](https://github.com/azlux/log2ram). 2. Reboot the system 3. View the error logs **Expected behavior** No errors and a working netbird interface **Additional context** ```/var/log/netbird``` is created at a certain point, but was not synced to the persistent /var/log (if available). So effectively, after a reboot, the ```/var/log/netbird``` directory does not exist. This in turn means it cannot be used for stdout and stderr. I tried creating it with an ```ExecStartPre``` using ```mkdir``` inside the unit file, but attaching the stdout and stderr apparently happens before that point and as such, errors with: aug 11 12:49:36 hostname systemd[8997]: netbird.service: Failed at step STDOUT spawning /usr/bin/mkdir: No such file or directory **Proposed solution** __Add__ this to the unit file, which ensures ```client.log``` can be created / updated: ExecStartPre=/usr/bin/mkdir /var/log/netbird __Remove__ the following lines, since that output should be captured inside of systemd (journalctl) anyway: StandardOutput=file:/var/log/netbird/netbird.out StandardError=file:/var/log/netbird/netbird.err
saavagebueno added the feature-requestsystem-compatibility-issue labels 2025-11-20 05:11:05 -05:00
saavagebueno commented 2025-11-20 05:11:06 -05:00
Author
Owner
Copy Link

@hg commented on GitHub (Nov 22, 2023):

For future reference: the canonical way to fix this is to add:

CacheDirectory=netbird
ConfigurationDirectory=netbird
LogDirectory=netbird
RuntimeDirectory=netbird
StateDirectory=netbird

under the [Service] section.

systemd will then make sure to create the appropriate directories and give your service full access to them before starting the daemon:

  • /var/cache/netbird
  • /etc/netbird
  • /var/log/netbird
  • /var/run/netbird
  • /var/lib/netbird

It's not immediately obvious how to add this to netbird service install since netbird relies on a third-party (not really) package for its service management, and the Option field I see there does not "accept" these keys.

@hg commented on GitHub (Nov 22, 2023): For future reference: the canonical way to fix this is to add: ```ini CacheDirectory=netbird ConfigurationDirectory=netbird LogDirectory=netbird RuntimeDirectory=netbird StateDirectory=netbird ``` under the `[Service]` section. systemd will then make sure to create the appropriate directories and give your service full access to them *before* starting the daemon: - `/var/cache/netbird` - `/etc/netbird` - `/var/log/netbird` - `/var/run/netbird` - `/var/lib/netbird` It's not immediately obvious how to add this to `netbird service install` since netbird relies on a third-party (not really) package for its service management, and the `Option` field I see there does not "accept" these keys.
saavagebueno commented 2025-11-20 05:11:06 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Feb 13, 2024):

it's LogsDirectory not LogDirectory, also currently only State and Runtime directories are used?

@nazarewk commented on GitHub (Feb 13, 2024): it's `LogsDirectory` not `LogDirectory`, also currently only `State` and `Runtime` directories are used?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label feature-request system-compatibility-issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#418
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?