-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Provide details when logging the error "Failed to retrieve client pool. " #8594
Comments
same question |
zmb3
added a commit
that referenced
this issue
Jun 16, 2022
Include the remote addr of the client to help cluster administrators identify the misbehaving client. Fixes #8594
github-actions bot
pushed a commit
that referenced
this issue
Jun 20, 2022
Include the remote addr of the client to help cluster administrators identify the misbehaving client. Fixes #8594
github-actions bot
pushed a commit
that referenced
this issue
Jun 20, 2022
Include the remote addr of the client to help cluster administrators identify the misbehaving client. Fixes #8594
github-actions bot
pushed a commit
that referenced
this issue
Jun 20, 2022
Include the remote addr of the client to help cluster administrators identify the misbehaving client. Fixes #8594
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
What happened:
Cluster was reconfigured with a different name . Some old nodes that were not re-configured continue to try to connect to the old cluster
What you expected to happen:
Error log prints details about the node that is trying to access . Like an IP address or hostname or some other identifying information.
Reproduction Steps
As minimally and precisely as possible, describe step-by-step how to reproduce the problem.
Server Details
teleport version
):6.2.3/etc/os-release
):In environments where teleport is not the only method of access , some servers might have stale teleport configurations and it is not possible to find the offending server.
The text was updated successfully, but these errors were encountered: