starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[Bug] headscale fails to start on full disk #916

New Issue
Closed
opened 2025-12-29 02:25:56 +01:00 by adam · 1 comment
adam commented 2025-12-29 02:25:56 +01:00
Owner
Copy Link

Originally created by @dotlambda on GitHub (Jan 22, 2025).

Is this a support request?

  • This is not a support request

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

If the hard drive containing headscale's SQLite database is 100% full, headscale fails to start with

2025-01-22T06:56:40+01:00 INF Opening database database=sqlite3 path=/var/lib/headscale/db.sqlite
2025-01-22T06:56:40+01:00 FTL github.com/juanfont/headscale/cmd/headscale/cli/serve.go:24 > Error initializing error="enabling foreign keys: disk I/O error (4874)"

Expected Behavior

Since headscale plays a potentially critical part in reaching the server whose disk is full (I luckily had plain Wireguard as a backup), it would be nice if it started regardless.

Steps To Reproduce

see above

Environment

- OS: NixOS 25.05
- Headscale version: 0.24.0
- Tailscale version: 1.78.1

Runtime environment

  • Headscale is behind a (reverse) proxy
  • Headscale runs in a container

Anything else?

No response

Originally created by @dotlambda on GitHub (Jan 22, 2025). ### Is this a support request? - [x] This is not a support request ### Is there an existing issue for this? - [x] I have searched the existing issues ### Current Behavior If the hard drive containing headscale's SQLite database is 100% full, headscale fails to start with ``` 2025-01-22T06:56:40+01:00 INF Opening database database=sqlite3 path=/var/lib/headscale/db.sqlite 2025-01-22T06:56:40+01:00 FTL github.com/juanfont/headscale/cmd/headscale/cli/serve.go:24 > Error initializing error="enabling foreign keys: disk I/O error (4874)" ``` ### Expected Behavior Since headscale plays a potentially critical part in reaching the server whose disk is full (I luckily had plain Wireguard as a backup), it would be nice if it started regardless. ### Steps To Reproduce see above ### Environment ```markdown - OS: NixOS 25.05 - Headscale version: 0.24.0 - Tailscale version: 1.78.1 ``` ### Runtime environment - [x] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ### Anything else? _No response_
adam added the bug label 2025-12-29 02:25:56 +01:00
adam closed this issue 2025-12-29 02:25:56 +01:00
adam commented 2025-12-29 02:25:57 +01:00
Author
Owner
Copy Link

@nblock commented on GitHub (Jan 22, 2025):

Headscale needs to persist its state to disk/database and thus requires free space.

You probably want to setup some monitoring to catch a filling disk early enough.

@nblock commented on GitHub (Jan 22, 2025): Headscale needs to persist its state to disk/database and thus requires free space. You probably want to setup some monitoring to catch a filling disk early enough.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#916
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?