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
teleport loads the license from /var/lib/teleport/license.pem
if it fails to load the license, it prints an actionable error
Current behavior:
teleport without a configuration file does not try to read the license from /var/lib/teleport/license.pem
teleport does not respect the --debug flag and only shows INFO logs
teleport swallows the real error and tells me
ERROR: initialization failed
# auth server requires a valid license file to start, please set the correct license_file path under auth_service section in your teleport
config or put the license into the default search location at /var/lib/teleport/license.pem
as soon as I create /etc/teleport.yaml everything starts to work
Bug details:
Teleport version 16.4.3 Enterprise
Recreation steps:
get an enterprise build and a valid license file
run teleport start --debug without a config file in /etc/teleport.yaml
Debug logs
The text was updated successfully, but these errors were encountered:
Prior to this change, the code that determines where to look for a
license file would only run when a config file is provided. When running
teleport start without a config file, the license file path would
be an empty string and loading would fail.
Closes#47764
zmb3
linked a pull request
Nov 17, 2024
that will
close
this issue
Prior to this change, the code that determines where to look for a
license file would only run when a config file is provided. When running
teleport start without a config file, the license file path would
be an empty string and loading would fail.
Closes#47764
Expected behavior:
Current behavior:
/var/lib/teleport/license.pem
--debug
flag and only showsINFO
logs/etc/teleport.yaml
everything starts to workBug details:
teleport start --debug
without a config file in/etc/teleport.yaml
The text was updated successfully, but these errors were encountered: