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.

Sign up for GitHub

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

Jump to bottom

Can't start telepresence #3582

Closed
Nefelum opened this issue Apr 22, 2024 · 3 comments
Closed

Can't start telepresence #3582

Nefelum opened this issue Apr 22, 2024 · 3 comments

Comments

@Nefelum
Copy link

Nefelum commented Apr 22, 2024

I don't know my configs, because that's my first experience with k8s on Windows with telepresence.
Log:
2024-04-22 23:44:28.1774 info daemon/session : -- Starting new session
2024-04-22 23:44:28.2636 info daemon/session : Connected to OSS Traffic Manager v2.17.0
2024-04-22 23:44:28.2636 info daemon/session : Connected to Manager 2.17.0
2024-04-22 23:44:28.2646 info daemon/session : also-proxy subnets []
2024-04-22 23:44:28.2646 info daemon/session : never-proxy subnets [127.0.0.1/32]
2024-04-22 23:44:28.2646 info daemon/session : Configuration reloaded
2024-04-22 23:44:29.2809 info daemon/session/network : also-proxy subnets []
2024-04-22 23:44:29.2809 info daemon/session/network : never-proxy subnets [127.0.0.1/32]
2024-04-22 23:44:29.2847 info daemon/session/network : Creating interface tel0
2024-04-22 23:44:29.3259 info stdlog : Using existing driver 0.14
2024-04-22 23:44:29.3291 info stdlog : Creating adapter
2024-04-22 23:44:29.4011 info daemon/session/network : Starting Endpoint
2024-04-22 23:44:29.4011 info daemon/session/network : also-proxy subnets []
2024-04-22 23:44:29.4011 info daemon/session/network : never-proxy subnets [127.0.0.1/32]
2024-04-22 23:44:29.4011 info daemon/session/network : Adding Service subnet 10.96.0.0/12
2024-04-22 23:44:29.4011 info daemon/session/network : Setting cluster DNS to 10.1.0.47
2024-04-22 23:44:29.4011 info daemon/session/network : Setting cluster domain to "cluster.local."
2024-04-22 23:44:42.8621 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:42.9683 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:43.0774 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:43.1864 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:43.2958 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:43.4042 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:43.5137 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:43.6230 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:43.7323 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:43.8395 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:43.9494 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:44.0587 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:44.1688 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:44.2752 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:44.3880 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:44.4922 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:44.6014 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:44.7092 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:44.8177 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:44.9272 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:45.0371 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:45.1471 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:45.2573 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:45.3655 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:45.4750 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:45.5845 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:45.6930 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:45.8012 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:45.9124 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:46.0206 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:46.1312 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:46.2405 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
2024-04-22 23:44:46.3499 error daemon/session/dns/RecursionCheck : unexpected error during recursion check: lookup tel2-recursion-check.kube-system.tel2-search: no such host
@Nefelum
Copy link
Author

Nefelum commented Apr 22, 2024

telepresence_logs.zip

@thallgren
Copy link
Contributor

thallgren commented Apr 30, 2024 •
edited

We've made several improvements in this area. Some of them are included in the 2.18.0 release and others are pending the next release. You can try three things.

  1. Upgrade to the latest OSS version 2.18.0 and see if that helps.
  2. If not, try building a new client from the latest on the release/v2 and use that.
  3. Sign up for a free trial of our enterprise version. It has higher release cadence.

@thallgren
Copy link
Contributor

Closing this, because no more info was provided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thallgren @Nefelum