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

[Bug] v0.23 does not work with PostgreSQL #716

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

Originally created by @simonszu on GitHub (May 25, 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

The startup of 0.23 apparently requires a certain postgresql database schema which is not present, even when upgrading from a 0.22 installation. It shows this error in the logs:

FTL Migration failed: FEHLER: Spalte »last_successful_update« von Relation »nodes« existiert nicht (SQLSTATE 42703) error="FEHLER: Spalte »last_successful_update« von Relation »nodes« existiert nicht (SQLSTATE 42703)"

Which roughly translates as "column last_successful_update from relation nodes does not exist".

This error occurs on a completely new database as well as upgrading from a 0.22 installation with an already pre-populated database (a tailnet and some nodes are present).

Expected Behavior

The headscale container comes up just fine, or is able to successfully complete the migration.

Steps To Reproduce

  1. Configure headscale to use postgres instead of sqlite
  2. Start a 0.23 container

Environment

- OS:Debian Bookworm
- Headscale version: 0.23.0-alpha11 and -alpha12
- Tailscale version: Does not matter yet

Runtime environment

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

Anything else?

No response

Originally created by @simonszu on GitHub (May 25, 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 The startup of 0.23 apparently requires a certain postgresql database schema which is not present, even when upgrading from a 0.22 installation. It shows this error in the logs: ``` FTL Migration failed: FEHLER: Spalte »last_successful_update« von Relation »nodes« existiert nicht (SQLSTATE 42703) error="FEHLER: Spalte »last_successful_update« von Relation »nodes« existiert nicht (SQLSTATE 42703)" ``` Which roughly translates as "column last_successful_update from relation nodes does not exist". This error occurs on a completely new database as well as upgrading from a 0.22 installation with an already pre-populated database (a tailnet and some nodes are present). ### Expected Behavior The headscale container comes up just fine, or is able to successfully complete the migration. ### Steps To Reproduce 1. Configure headscale to use postgres instead of sqlite 2. Start a 0.23 container ### Environment ```markdown - OS:Debian Bookworm - Headscale version: 0.23.0-alpha11 and -alpha12 - Tailscale version: Does not matter yet ``` ### Runtime environment - [ ] Headscale is behind a (reverse) proxy - [X] Headscale runs in a container ### Anything else? _No response_
adam added the bug label 2025-12-29 02:22:47 +01:00
adam closed this issue 2025-12-29 02:22:47 +01:00
adam commented 2025-12-29 02:22:48 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (May 27, 2024):

Fix is up in https://github.com/juanfont/headscale/pull/1959, we checked the postgres error by string, and since you have yours in German, it did not match.

I would recommend you to change the postgres language to english, we will try to avoid this in the future, but since there is no uniform error checking for us in postgres, I will not rule out that this can happen again in the future, if there is a larger necessity for a check like this, then we might opt for not supporting other languages if necessary.

@kradalby commented on GitHub (May 27, 2024): Fix is up in https://github.com/juanfont/headscale/pull/1959, we checked the postgres error by string, and since you have yours in German, it did not match. I would recommend you to change the postgres language to english, we will try to avoid this in the future, but since there is no uniform error checking for us in postgres, I will not rule out that this can happen again in the future, if there is a larger necessity for a check like this, then we might opt for not supporting other languages if necessary.
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#716
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?