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

Sqlite and Sqlite3 db types fail to start with "out of memory" on v0.23.0-alpha4 #642

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

Originally created by @Nickiel12 on GitHub (Feb 17, 2024).

Bug description

After updating from headscale v0.23.0-alpha3, to v0.23.0-alpha4, I am unable to start headscale and encounter this error in my journalctl output:

FTL github.com/juanfont/headscale/cmd/headscale/cli/server.go:21 > Error initializing error="unable to open database file: out of memory (14)"

A side note, but I also had to change the "settings.db_type" setting to "settings.database.type" in my nix config. It would be nice to implement a depreciation warning on this setting in the repository's flake.nix.

Environment

  • headscale v0.23.0-alpha4
  • Tailscale 1.60.0
  • NixOS 24.05 - unstable

I have nginx running with a proxypass to headscale, but I've been succesfully using that for a while

To Reproduce

Install headscale v0.23.0-alpha4 with the following settings:

  services.headscale = {
    package = headscale.packages.${pkgs.system}.headscale; // using the flake
    enable = true;
    address = "0.0.0.0";
    port = 8082;
    settings = {
      server_url = "https://${domain}";
      database.type = "sqlite3";
      dns_config = {
        base_domain = baseDomain;
        extra_records = tailscale_dns_entries;
      };
      derp = {
        auto_update_enable = true;
        update_frequency = "24h";
      };
    };
  };
Originally created by @Nickiel12 on GitHub (Feb 17, 2024). ## Bug description After updating from headscale v0.23.0-alpha3, to v0.23.0-alpha4, I am unable to start headscale and encounter this error in my journalctl output: `FTL github.com/juanfont/headscale/cmd/headscale/cli/server.go:21 > Error initializing error="unable to open database file: out of memory (14)"` A side note, but I also had to change the "settings.db_type" setting to "settings.database.type" in my nix config. It would be nice to implement a depreciation warning on this setting in the repository's flake.nix. ## Environment - headscale v0.23.0-alpha4 - Tailscale 1.60.0 - NixOS 24.05 - unstable I have nginx running with a proxypass to headscale, but I've been succesfully using that for a while ## To Reproduce Install headscale v0.23.0-alpha4 with the following settings: ```nix services.headscale = { package = headscale.packages.${pkgs.system}.headscale; // using the flake enable = true; address = "0.0.0.0"; port = 8082; settings = { server_url = "https://${domain}"; database.type = "sqlite3"; dns_config = { base_domain = baseDomain; extra_records = tailscale_dns_entries; }; derp = { auto_update_enable = true; update_frequency = "24h"; }; }; }; ```
adam added the bug label 2025-12-29 02:21:32 +01:00
adam closed this issue 2025-12-29 02:21:32 +01:00
adam commented 2025-12-29 02:21:33 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Feb 18, 2024):

Duplicate of #1761, fixed in main.

@kradalby commented on GitHub (Feb 18, 2024): Duplicate of #1761, fixed in main.
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#642
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?