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] Error initializing error="enabling foreign keys: disk I/O error #801

New Issue
Closed
opened 2025-12-29 02:24:11 +01:00 by adam · 3 comments
adam commented 2025-12-29 02:24:11 +01:00
Owner
Copy Link

Originally created by @mimnix on GitHub (Sep 20, 2024).

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

Hello,
I'm experiencing an issue in the upgrade from 0.23.0-beta3 to 0.23.0-beta4, using sqlite as database. Headscale doesn't start with the error:

headscale     | 2024-09-19T23:20:19Z INF Opening database database=sqlite3 path=/var/lib/headscale/db.sqlite
headscale     | 2024-09-19T23:20:19Z FTL home/runner/work/headscale/headscale/cmd/headscale/cli/serve.go:24 > Error initializing error="enabling foreign keys: disk I/O error (5386)"
headscale     | 2024-09-19T23:20:20Z INF Opening database database=sqlite3 path=/var/lib/headscale/db.sqlite
headscale     | 2024-09-19T23:20:20Z FTL home/runner/work/headscale/headscale/cmd/headscale/cli/serve.go:24 > Error initializing error="enabling foreign keys: disk I/O error (5386)"
headscale     | 2024-09-19T23:20:20Z INF Opening database database=sqlite3 path=/var/lib/headscale/db.sqlite

Any suggestions? Thank you!

Expected Behavior

A successful upgrade from 0.23.0-beta3 to 0.23.0-beta4

Steps To Reproduce

  1. using headscale docker image headscale/headscale:0.23.0-beta3, setup the server (with sqlite as db) and add some clients
  2. Stop the stack/container and change the image tag to headscale/headscale:0.23.0-beta4
  3. Start the stack/container again

Environment

- OS: Oracle Linux Server release 8.10
- Headscale version: 0.23.0-beta.4
- Tailscale version: 1.74.0

Runtime environment

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

Anything else?

No response

Originally created by @mimnix on GitHub (Sep 20, 2024). ### 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 Hello, I'm experiencing an issue in the upgrade from `0.23.0-beta3` to `0.23.0-beta4`, using sqlite as database. Headscale doesn't start with the error: ``` headscale | 2024-09-19T23:20:19Z INF Opening database database=sqlite3 path=/var/lib/headscale/db.sqlite headscale | 2024-09-19T23:20:19Z FTL home/runner/work/headscale/headscale/cmd/headscale/cli/serve.go:24 > Error initializing error="enabling foreign keys: disk I/O error (5386)" headscale | 2024-09-19T23:20:20Z INF Opening database database=sqlite3 path=/var/lib/headscale/db.sqlite headscale | 2024-09-19T23:20:20Z FTL home/runner/work/headscale/headscale/cmd/headscale/cli/serve.go:24 > Error initializing error="enabling foreign keys: disk I/O error (5386)" headscale | 2024-09-19T23:20:20Z INF Opening database database=sqlite3 path=/var/lib/headscale/db.sqlite ``` Any suggestions? Thank you! ### Expected Behavior A successful upgrade from `0.23.0-beta3` to `0.23.0-beta4` ### Steps To Reproduce 1. using headscale docker image headscale/headscale:0.23.0-beta3, setup the server (with sqlite as db) and add some clients 2. Stop the stack/container and change the image tag to headscale/headscale:0.23.0-beta4 3. Start the stack/container again ### Environment ```markdown - OS: Oracle Linux Server release 8.10 - Headscale version: 0.23.0-beta.4 - Tailscale version: 1.74.0 ``` ### Runtime environment - [X] Headscale is behind a (reverse) proxy - [X] Headscale runs in a container ### Anything else? _No response_
adam added the stalebug labels 2025-12-29 02:24:11 +01:00
adam closed this issue 2025-12-29 02:24:11 +01:00
adam commented 2025-12-29 02:24:11 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Sep 20, 2024):

I'm not able to reproduce this, can you send me a copy of a database where this is happening? preferably one that is as minimal as possible.

@kradalby commented on GitHub (Sep 20, 2024): I'm not able to reproduce this, can you send me a copy of a database where this is happening? preferably one that is as minimal as possible.
adam commented 2025-12-29 02:24:11 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 25, 2024):

This issue is stale because it has been open for 90 days with no activity.

@github-actions[bot] commented on GitHub (Dec 25, 2024): This issue is stale because it has been open for 90 days with no activity.
adam commented 2025-12-29 02:24:12 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 1, 2025):

This issue was closed because it has been inactive for 14 days since being marked as stale.

@github-actions[bot] commented on GitHub (Jan 1, 2025): This issue was closed because it has been inactive for 14 days since being marked as stale.
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 stale
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#801
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?