Skip to content
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

Closed
anurag-work opened this issue Oct 13, 2021 · 1 comment · Fixed by #13585
Closed

Provide details when logging the error "Failed to retrieve client pool. " #8594

anurag-work opened this issue Oct 13, 2021 · 1 comment · Fixed by #13585
Labels
bug error-msg Improving customer facing error messages.

Comments

@anurag-work
Copy link

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.

  1. Setup a cluster and add a node to the cluster
  2. Reconfigure the cluster with the FQDN/IP but change the cluster name. Don't reconfigure the node to use the new cluster
  3. New cluster is full of error messages but with no information regarding the node .
Failed to retrieve client pool. Client cluster "old-cluster-name", target cluster "new-cluster-name"

Server Details

  • Teleport version (run teleport version):6.2.3
  • Server OS (e.g. from /etc/os-release):
  • Where are you running Teleport? (e.g. AWS, GCP, Dedicated Hardware):
  • Additional details:

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.

@qixiangyang
Copy link

same question

@zmb3 zmb3 added error-msg Improving customer facing error messages. time-to-value labels Jun 8, 2022
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
zmb3 added a commit that referenced this issue Jun 28, 2022
#13674)

Improve log message when we fail to retrieve the client cert pool

Include the remote addr of the client to help cluster administrators
identify the misbehaving client.

Fixes #8594
zmb3 added a commit that referenced this issue Jun 28, 2022
…ol (#13676)

Improve log message when we fail to retrieve the client cert pool

Include the remote addr of the client to help cluster administrators
identify the misbehaving client.

Fixes #8594
zmb3 added a commit that referenced this issue Jun 29, 2022
#13675)

Improve log message when we fail to retrieve the client cert pool

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
Labels
bug error-msg Improving customer facing error messages.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants