You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Is this a support request?
Is there an existing issue for this?
Current Behavior
Debug and trace messages are always printed when running
headscale nodes list
with 0.23.0-beta.4. The commandheadscale 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
/var/lib/headscale
to allow local startsgrep -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
./releases/headscale_0.23.0-beta.4_linux_amd64 -c config-example.yaml serve
./releases/headscale_0.23.0-beta.4_linux_amd64 -c config-example.yaml nodes list
Try with headscale 0.23.0-beta3
./releases/headscale_0.23.0-beta3_linux_amd64 -c config-example.yaml serve
./releases/headscale_0.23.0-beta3_linux_amd64 -c config-example.yaml nodes list
Environment
Runtime environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: