Comments (4)
Hi @qiaoenxin , can you check your IP table (netstat -rn) to see if Telepresence added subnets / routes. If it added the routes it will add your pod subnets and your service subnets in your cluster, so we'd like to check that first.
Can you also share the output of ‘telepresence connect’?
from telepresence.
We would also recommend trying telepresence quit -s
, which you might have to do multiple times to remove old root daemon processes. If that doesn't help, try checking for any old Telepresence processes and manually killing them.
from telepresence.
Hey @qiaoenxin , can you please try setting the loglevel to debug in your %APPDATA%\telepresence\config.yml
then do a telepresence quit
followed by a telepresence connect
and provide logs again?
The entry should look like this:
logLevels:
userDaemon: debug
rootDaemon: debug
from telepresence.
Hi @qiaoenxin , can you check your IP table (netstat -rn) to see if Telepresence added subnets / routes. If it added the routes it will add your pod subnets and your service subnets in your cluster, so we'd like to check that first.
Can you also share the output of ‘telepresence connect’?
I try to do that. The subnets / routes do not exist.
0.0.0.0 0.0.0.0 192.168.31.254 192.168.30.54 35
127.0.0.0 255.0.0.0 在链路上 127.0.0.1 331
127.0.0.1 255.255.255.255 在链路上 127.0.0.1 331
127.255.255.255 255.255.255.255 在链路上 127.0.0.1 331
169.254.0.0 255.255.0.0 在链路上 169.254.97.92 261
169.254.97.92 255.255.255.255 在链路上 169.254.97.92 261
169.254.255.255 255.255.255.255 在链路上 169.254.97.92 261
192.168.11.0 255.255.255.0 在链路上 192.168.11.1 291
192.168.11.1 255.255.255.255 在链路上 192.168.11.1 291
192.168.11.255 255.255.255.255 在链路上 192.168.11.1 291
192.168.30.0 255.255.254.0 在链路上 192.168.30.54 291
192.168.30.54 255.255.255.255 在链路上 192.168.30.54 291
192.168.31.255 255.255.255.255 在链路上 192.168.30.54 291
192.168.56.0 255.255.255.0 在链路上 192.168.56.1 291
192.168.56.1 255.255.255.255 在链路上 192.168.56.1 291
192.168.56.255 255.255.255.255 在链路上 192.168.56.1 291
224.0.0.0 240.0.0.0 在链路上 127.0.0.1 331
224.0.0.0 240.0.0.0 在链路上 192.168.56.1 291
224.0.0.0 240.0.0.0 在链路上 192.168.11.1 291
224.0.0.0 240.0.0.0 在链路上 192.168.30.54 291
224.0.0.0 240.0.0.0 在链路上 169.254.97.92 261
255.255.255.255 255.255.255.255 在链路上 127.0.0.1 331
255.255.255.255 255.255.255.255 在链路上 192.168.56.1 291
255.255.255.255 255.255.255.255 在链路上 192.168.11.1 291
255.255.255.255 255.255.255.255 在链路上 192.168.30.54 291
255.255.255.255 255.255.255.255 在链路上 169.254.97.92 261
C:\Users\qiaoenxin>telepresence connect
Launching Telepresence User Daemon
Launching Telepresence Root Daemon
telepresence connect: error: connector.Connect: failed to connect to root daemon: rpc error: code = DeadlineExceeded desc = context deadline exceeded
See logs for details (2 errors found): "C:\\Users\\qiaoenxin\\AppData\\Local\\telepresence\\logs\\daemon.log"
If you think you have encountered a bug, please run `telepresence gather-logs` and attach the telepresence_logs.zip to your github issue or create a new one: https://github.com/telepresenceio/telepresence/issues/new?template=Bug_report.md .
C:\\Users\\qiaoenxin\\AppData\\Local\\telepresence\\logs\\daemon.log
2024-07-25 14:11:33.6587 info ---
2024-07-25 14:11:33.6587 info Telepresence daemon v2.18.0 (api v3) starting...
2024-07-25 14:11:33.6587 info PID is 15240
2024-07-25 14:11:33.6587 info
2024-07-25 14:11:33.6603 debug Listener opened
2024-07-25 14:11:33.7337 info daemon/server-grpc : gRPC server started
2024-07-25 14:11:37.8230 debug daemon/server-grpc/conn=4 : Received gRPC Connect
2024-07-25 14:11:37.8230 info daemon/session : -- Starting new session
2024-07-25 14:11:37.8251 debug daemon/session : k8sPortForwardDialer.Dial(ctx, "svc/traffic-manager.ambassador:api")
2024-07-25 14:11:37.8507 debug daemon/session : k8sPortForwardDialer.dial(ctx, Pod./traffic-manager-7474bbb694-tgdd6.ambassador, 8081)
2024-07-25 14:11:37.8512 debug daemon/session : k8sPortForwardDialer.spdyDial(ctx, Pod./traffic-manager-7474bbb694-tgdd6.ambassador)
2024-07-25 14:11:37.9466 info daemon/session : Connected to OSS Traffic Manager v2.18.0
2024-07-25 14:11:37.9466 info daemon/session : Connected to Manager 2.18.0
2024-07-25 14:11:37.9503 debug daemon/session : Creating session with id session_id:"a67ab01b-1289-4bfa-bd44-a07adb5fb471" cluster_id:"589f450c-a912-448d-b27e-b7434fb20b30" install_id:"6c73228c-81c1-4b9b-b212-bef06c778195"
2024-07-25 14:11:37.9503 info daemon/session : also-proxy subnets []
2024-07-25 14:11:37.9503 info daemon/session : never-proxy subnets [170.18.9.17/32]
2024-07-25 14:11:37.9503 info daemon/session : allow-conflicting subnets []
2024-07-25 14:11:37.9514 info daemon/session : Configuration reloaded
2024-07-25 14:11:37.9514 debug daemon/session : Returning session from new session session_id:"a67ab01b-1289-4bfa-bd44-a07adb5fb471" cluster_id:"589f450c-a912-448d-b27e-b7434fb20b30" install_id:"6c73228c-81c1-4b9b-b212-bef06c778195"
2024-07-25 14:11:37.9556 info daemon/session/network : also-proxy subnets []
2024-07-25 14:11:37.9556 info daemon/session/network : never-proxy subnets [170.18.9.17/32]
2024-07-25 14:11:37.9556 info daemon/session/network : allow-conflicting subnets []
2024-07-25 14:11:37.9556 debug daemon/session/network : Performing pod connectivity check on IP 241.255.0.164 with timeout 500ms
2024-07-25 14:11:37.9576 debug daemon/session/agentPods : WatchAgentPods starting
2024-07-25 14:11:38.4711 debug daemon/session/network : Will proxy pods (context deadline exceeded)
2024-07-25 14:11:38.4711 debug daemon/session/network : Performing service connectivity check on https://241.254.79.250:443/healthz with Host agent-injector.ambassador and timeout 500ms
2024-07-25 14:11:38.4717 debug daemon/session/network : Will proxy services (Get "https://241.254.79.250:443/healthz": dial tcp 241.254.79.250:443: connectex: A socket operation was attempted to an unreachable network.)
2024-07-25 14:11:38.4717 debug daemon/session/network : WatchClusterInfo update
2024-07-25 14:11:38.4717 info daemon/session/network : Adding service subnet 241.254.0.0/16
2024-07-25 14:11:38.4717 info daemon/session/network : Adding pod subnet 241.255.0.0/24
2024-07-25 14:11:38.4863 info daemon/session/network : Creating interface tel0
2024-07-25 14:11:38.5774 info stdlog : Using existing driver 0.14
2024-07-25 14:11:38.5871 info stdlog : Creating adapter
2024-07-25 14:11:39.1399 info daemon/session/network : Setting cluster DNS to 241.255.0.164
2024-07-25 14:11:39.1399 info daemon/session/network : Setting cluster domain to "cluster.local."
2024-07-25 14:11:39.1410 info daemon/session/network : Dropping never-proxy "170.18.9.17/32" because it is not routed
2024-07-25 14:11:39.1449 info daemon/session/network : Starting Endpoint
2024-07-25 14:11:39.1981 info stdlog : Removed orphaned adapter "tel0 1"
2024-07-25 14:11:41.0442 error daemon/session/network : failed to add subnet 241.254.0.0/16: The parameter is incorrect.
2024-07-25 14:11:41.0442 error daemon/session/network : failed to add subnet 241.255.0.0/24: The parameter is incorrect.
2024-07-25 14:11:41.0442 debug daemon/session/dns/Server : SetDNS clusterDomain: "cluster.local.", server: 241.255.0.164, searchList: [tel2-search]
2024-07-25 14:11:41.0453 debug daemon/session/dns/Server : setting registry value System\CurrentControlSet\Services\Tcpip\Parameters\SearchList to tel2-search
2024-07-25 14:11:41.0649 debug daemon/session/dns/Server : SetDNS done
2024-07-25 14:11:41.0649 debug daemon/session/dns/SearchPaths : Performing initial recursion check with tel2-recursion-check.tel2-search
2024-07-25 14:12:01.2935 error daemon/session/dns/SearchPaths : DNS doesn't seem to work properly
2024-07-25 14:12:01.2935 debug daemon/session/dns/SearchPaths : Recursion check finished
from telepresence.
Related Issues (20)
- Connecting in Windows WSL with --docker option does not succeed HOT 1
- ReportMetrics failed errors HOT 2
- not able to use telepresence with m3 chip HOT 1
- Provide Homebrew release of OSS version "tel2oss" of Telepresence HOT 1
- Unable to install and run telepresence inside a docker container HOT 7
- [MacOS] Telepresence opens many AWS auth request tabs in the browser even while the computer is asleep HOT 5
- allowConflictingSubnets not recognised in laptop config.yml HOT 2
- DNS Errors after connecting with telepresence on Windows HOT 28
- Bad merge causes helm AGENT_SECURITY_CONTEXT variable to not get rendered
- Unable to intercept services when using telepresence intercept HOT 2
- telepresence intercept: error: unknown flag: --http-header HOT 1
- telepresence helm install: error: the helm operation timed out. The current timeout 30s can be configured as "timeouts.helm" in "/root/.config/telepresence/config.yml" HOT 2
- Add support for argo rollouts HOT 2
- Command `telepresence helm install` not obeying value overrides HOT 1
- Upload-traces command sends gRPC messages larger than the default max size HOT 1
- Helm Chart Deployment Fails with Nil Pointer Errors on Nullable Values HOT 2
- Docker volume mounts fail after ending docker-run with <ctrl>-c HOT 1
- Volumes mounted only from one container HOT 6
- Helm upgrade issue 2.19.6 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from telepresence.