-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node with empty disco_key in DB prevents to start headscale #1816
Comments
Fixed juanfont#1816 Signed-off-by: Kristoffer Dalby <[email protected]>
Fixed #1816 Signed-off-by: Kristoffer Dalby <[email protected]>
@kradalby I know this issue has been resolved for a while, but I have two separate Headscale instances that I upgraded to v0.23.0 today. One upgrade went smoothly, but the other logged the error repeatedly for all clients:
I really appreciate the work you do! I'm really excited for v0.23.0. Edit: Interestingly, the same error was logged during startup.
I wonder if the migration from machines to nodes failed because of the error? Another Edit: Yep, I think the migration may have failed. I noticed there was a device that hadn't connected in ~5 months, and it had an empty |
Bug description
On updating headscale from 0.22.3 to 0.23.0-alpha5 headscale fails to starts due incorrect entry in database. One of nodes had empty disco_key ("disco_key:"). This entry is causing to headscale fail to start:
After manually deleting that node in database headscale starts normally. I have no idea how I got that node in database, but in 0.22.3 this error is not critical in order to start headscale.
Environment
To Reproduce
Have node with empty disco_key in database, restart Headscale.
Logs and attachments
The text was updated successfully, but these errors were encountered: