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] headscale nodes list always prints debug/trace messages #789

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

Originally created by @nblock on GitHub (Sep 9, 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

Debug and trace messages are always printed when running headscale nodes list with 0.23.0-beta.4. The command headscale serve seems to work, though.

This is a regression since 0.23.0-beta3.

Expected Behavior

Only print debug/trace when specified in the configuration

Steps To Reproduce

Prepare configuration

  • Download example config and strip /var/lib/headscale to allow local starts
  • grep -A3 "^log:" config-example.yaml
log:
  # Output formatting for logs: text or json
  format: text
  level: info

Try with headscale 0.23.0-beta.4

  • Download headscale 0.23.0-beta.4
  • Run (terminal 1): ./releases/headscale_0.23.0-beta.4_linux_amd64 -c config-example.yaml serve
  • Run (terminal 2): ./releases/headscale_0.23.0-beta.4_linux_amd64 -c config-example.yaml nodes list
2024-09-09T20:34:17+02:00 DBG Setting timeout timeout=5000
2024-09-09T20:34:17+02:00 DBG HEADSCALE_CLI_ADDRESS environment is not set, connecting to unix socket. socket=headscale.sock
2024-09-09T20:34:17+02:00 TRC ../../../runner/work/headscale/headscale/cmd/headscale/cli/utils.go:121 > Connecting via gRPC address=headscale.sock
ID | Hostname | Name | MachineKey | NodeKey | User | IP addresses | Ephemeral | Last seen | Expiration | Connected | Expired

Try with headscale 0.23.0-beta3

  • Download headscale 0.23.0-beta3
  • Run (terminal 1): ./releases/headscale_0.23.0-beta3_linux_amd64 -c config-example.yaml serve
  • Run (terminal 2): ./releases/headscale_0.23.0-beta3_linux_amd64 -c config-example.yaml nodes list
2024-09-09T20:40:38+02:00 WRN 
WARN: The "dns.use_username_in_magic_dns" configuration key is deprecated and has been removed. Please see the changelog for more details.

ID | Hostname | Name | MachineKey | NodeKey | User | IP addresses | Ephemeral | Last seen | Expiration | Connected | Expired

Environment

- OS: Debian 12
- Headscale version: 0.23.0-beta.4
- Tailscale version: -

Runtime environment

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

Anything else?

No response

Originally created by @nblock on GitHub (Sep 9, 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 Debug and trace messages are always printed when running `headscale nodes list` with 0.23.0-beta.4. The command `headscale serve` seems to work, though. This is a regression since 0.23.0-beta3. ### Expected Behavior Only print debug/trace when specified in the configuration ### Steps To Reproduce #### Prepare configuration * Download example config and strip `/var/lib/headscale` to allow local starts * `grep -A3 "^log:" config-example.yaml` ```bash log: # Output formatting for logs: text or json format: text level: info ```` #### Try with headscale 0.23.0-beta.4 * Download headscale 0.23.0-beta.4 * Run (terminal 1): `./releases/headscale_0.23.0-beta.4_linux_amd64 -c config-example.yaml serve` * Run (terminal 2): `./releases/headscale_0.23.0-beta.4_linux_amd64 -c config-example.yaml nodes list` ``` 2024-09-09T20:34:17+02:00 DBG Setting timeout timeout=5000 2024-09-09T20:34:17+02:00 DBG HEADSCALE_CLI_ADDRESS environment is not set, connecting to unix socket. socket=headscale.sock 2024-09-09T20:34:17+02:00 TRC ../../../runner/work/headscale/headscale/cmd/headscale/cli/utils.go:121 > Connecting via gRPC address=headscale.sock ID | Hostname | Name | MachineKey | NodeKey | User | IP addresses | Ephemeral | Last seen | Expiration | Connected | Expired ``` #### Try with headscale 0.23.0-beta3 * Download headscale 0.23.0-beta3 * Run (terminal 1): `./releases/headscale_0.23.0-beta3_linux_amd64 -c config-example.yaml serve` * Run (terminal 2): `./releases/headscale_0.23.0-beta3_linux_amd64 -c config-example.yaml nodes list` ``` 2024-09-09T20:40:38+02:00 WRN WARN: The "dns.use_username_in_magic_dns" configuration key is deprecated and has been removed. Please see the changelog for more details. ID | Hostname | Name | MachineKey | NodeKey | User | IP addresses | Ephemeral | Last seen | Expiration | Connected | Expired ``` ### Environment ```markdown - OS: Debian 12 - Headscale version: 0.23.0-beta.4 - Tailscale version: - ``` ### Runtime environment - [ ] Headscale is behind a (reverse) proxy - [ ] Headscale runs in a container ### Anything else? _No response_
adam added the bug label 2025-12-29 02:24:01 +01:00
adam closed this issue 2025-12-29 02:24:01 +01:00
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#789
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?