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

Headscale keeps repeating prompts that there are no logs with nodekey present。 #548

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

Originally created by @liangyoufeng on GitHub (Aug 30, 2023).

Bug description

Hello, I found that this type of information is constantly being output in the headscale log. I have checked the machines table information in db.sqlite and found that it cannot match. However, I have checked the historical records and indeed registered this nodekey. At the same time, the terminal I tested has also deleted this record. Why does it keep reporting this non-existent issue? Restarting the tailscale client and headscale server does not solve this error log, as there are no issues with functionality or network connectivity. I hope there is a solution, thank you.

Environment

  • OS: Centos7.9
  • Headscale version: 0.22.3
  • Tailscale version: 1.46.1
  • Headscale runs in a container

To Reproduce

The log is as follows:

2023-08-30T10:01:31Z WRN Ignoring request, cannot find machine with key nodekey:6663bc68d9bfaf4cb98ea14a96f773185956b7bf4d662311d7d46c2634a53050 handler=NoisePollNetMap
2023-08-30T10:02:08Z WRN Ignoring request, cannot find machine with key nodekey:6663bc68d9bfaf4cb98ea14a96f773185956b7bf4d662311d7d46c2634a53050 handler=NoisePollNetMap
2023-08-30T10:02:38Z WRN Ignoring request, cannot find machine with key nodekey:6663bc68d9bfaf4cb98ea14a96f773185956b7bf4d662311d7d46c2634a53050 handler=NoisePollNetMap

Originally created by @liangyoufeng on GitHub (Aug 30, 2023). <!-- Before posting a bug report, discuss the behaviour you are expecting with the Discord community to make sure that it is truly a bug. The issue tracker is not the place to ask for support or how to set up Headscale. Bug reports without the sufficient information will be closed. Headscale is a multinational community across the globe. Our language is English. All bug reports needs to be in English. --> ## Bug description <!-- A clear and concise description of what the bug is. Describe the expected bahavior and how it is currently different. If you are unsure if it is a bug, consider discussing it on our Discord server first. --> Hello, I found that this type of information is constantly being output in the headscale log. I have checked the machines table information in db.sqlite and found that it cannot match. However, I have checked the historical records and indeed registered this nodekey. At the same time, the terminal I tested has also deleted this record. Why does it keep reporting this non-existent issue? Restarting the tailscale client and headscale server does not solve this error log, as there are no issues with functionality or network connectivity. I hope there is a solution, thank you. ## Environment <!-- Please add relevant information about your system. For example: - Version of headscale used - Version of tailscale client - OS (e.g. Linux, Mac, Cygwin, WSL, etc.) and version - Kernel version - The relevant config parameters you used - Log output --> - OS: Centos7.9 - Headscale version: 0.22.3 - Tailscale version: 1.46.1 <!-- We do not support running Headscale in a container nor behind a (reverse) proxy. If either of these are true for your environment, ask the community in Discord instead of filing a bug report. --> - [ ] Headscale runs in a container ## To Reproduce <!-- Steps to reproduce the behavior. --> The log is as follows: 2023-08-30T10:01:31Z WRN Ignoring request, cannot find machine with key nodekey:6663bc68d9bfaf4cb98ea14a96f773185956b7bf4d662311d7d46c2634a53050 handler=NoisePollNetMap 2023-08-30T10:02:08Z WRN Ignoring request, cannot find machine with key nodekey:6663bc68d9bfaf4cb98ea14a96f773185956b7bf4d662311d7d46c2634a53050 handler=NoisePollNetMap 2023-08-30T10:02:38Z WRN Ignoring request, cannot find machine with key nodekey:6663bc68d9bfaf4cb98ea14a96f773185956b7bf4d662311d7d46c2634a53050 handler=NoisePollNetMap
adam added the stalebug labels 2025-12-29 02:19:51 +01:00
adam closed this issue 2025-12-29 02:19:51 +01:00
adam commented 2025-12-29 02:19:51 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 11, 2023):

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

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

@github-actions[bot] commented on GitHub (Dec 19, 2023):

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

@github-actions[bot] commented on GitHub (Dec 19, 2023): This issue was closed because it has been inactive for 14 days since being marked as stale.
adam commented 2025-12-29 02:19:52 +01:00
Author
Owner
Copy Link

@ZacharyRen77 commented on GitHub (Jul 31, 2024):

do you solve this problem？

@ZacharyRen77 commented on GitHub (Jul 31, 2024): do you solve this problem？
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#548
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?