telepresence: error: connector service did not start: timeout while waiting for connector to start

[jiangxiaoqiang]

Describe the bug

Today I upgrade the telepresence from 2.6.8 to 2.7.1 using this command in macos 12.4:

➜  cruise-open git:(main) brew upgrade datawire/blackbird/telepresence-arm64
Warning: No remote 'origin' in /opt/homebrew/Library/Taps/homebrew/homebrew-services, skipping update!
Running `brew update --auto-update`...
==> Upgrading 1 outdated package:
datawire/blackbird/telepresence-arm64 2.6.8 -> 2.7.1
==> Downloading https://app.getambassador.io/download/tel2/darwin/arm64/2.7.1/telepresence
######################################################################## 100.0%
==> Upgrading datawire/blackbird/telepresence-arm64
  2.6.8 -> 2.7.1

🍺  /opt/homebrew/Cellar/telepresence-arm64/2.7.1: 3 files, 74MB, built in 1 second
==> Running `brew cleanup telepresence-arm64`...
Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).
Removing: /opt/homebrew/Cellar/telepresence-arm64/2.6.8... (3 files, 73.0MB)
Removing: /Users/xiaoqiangjiang/Library/Caches/Homebrew/telepresence-arm64--2.6.8... (73.0MB)
➜  cruise-open git:(main) telepresence connect
version mismatch. Client v2.7.1 != User Daemon v2.6.8, please run 'telepresence quit -u' and reconnect
➜  cruise-open git:(main) telepresence quit -u
Telepresence Network disconnecting...done
Telepresence Traffic Manager quitting...done
➜  cruise-open git:(main) telepresence connect
telepresence: error: version mismatch. Client v2.7.1 != Root Daemon v2.6.8, please run 'telepresence quit -r' and reconnect
➜  cruise-open git:(main) telepresence quit -r
Telepresence Network quitting...done
Telepresence Traffic Manager is already disconnected%
➜  cruise-open git:(main) telepresence connect
Launching Telepresence Root Daemon
Need root privileges to run: /opt/homebrew/bin/telepresence daemon-foreground /Users/xiaoqiangjiang/Library/Logs/telepresence '/Users/xiaoqiangjiang/Library/Application Support/telepresence'
Password:
Launching Telepresence User Daemon
telepresence: error: connector service did not start: timeout while waiting for connector to start
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 .
➜  cruise-open git:(main)

what should I do to fixed this problem?

[lyubomirr]

Did you manage to find a solution, I'm getting the same error.

[jiangxiaoqiang]

no, I did not find the solution.

[cindymullins-dw]

Hi @jiangxiaoqiang , sometimes this can happen for example if the client is upgraded while the root daemon is still running and it can result in a mismatched state. Could you please try the commands below and let us know if that helps? telepresence quit -ur sudo pkill -SIGTERM -f daemon-foreground pkill -SIGTERM -f connector-foreground telepresence connect

[jiangxiaoqiang]

Hi @jiangxiaoqiang , sometimes this can happen for example if the client is upgraded while the root daemon is still running and it can result in a mismatched state. Could you please try the commands below and let us know if that helps? telepresence quit -ur sudo pkill -SIGTERM -f daemon-foreground pkill -SIGTERM -f connector-foreground telepresence connect

I have tried to upgrade to 2.8.2 and run the command what you have told but still could not fixed this error. still the same problem.

[etokarev]

Hi @jiangxiaoqiang , sometimes this can happen for example if the client is upgraded while the root daemon is still running and it can result in a mismatched state. Could you please try the commands below and let us know if that helps? telepresence quit -ur sudo pkill -SIGTERM -f daemon-foreground pkill -SIGTERM -f connector-foreground telepresence connect

Hi, I encountered a simular issue after a fresh install on a Silicon MBP :

telepresence connect
Launching Telepresence User Daemon
telepresence connect: error: connector service did not start: timeout while waiting for connector to start
failed to scan daemon logs: open /Users/****/Library/Logs/telepresence/daemon.log: no such file or directory

See logs for details (2 errors found): "/Users/****/Library/Logs/telepresence/connector.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 .

The app log:

2022-11-16 17:34:31.9776 info    ---
2022-11-16 17:34:31.9777 info    Telepresence Connector v2.9.2 (api v3) starting...
2022-11-16 17:34:31.9777 info    PID is 15781
2022-11-16 17:34:31.9777 info    
2022-11-16 17:34:31.9943 info    connector/server-grpc : gRPC server started
2022-11-16 17:34:31.9945 error   connector/refresh-token : goroutine "/connector/refresh-token" exited with error: lstat /Users/****/Library/Caches/telepresence: no such file or directory
2022-11-16 17:34:31.9945 info    connector:shutdown_logger : shutting down (gracefully)...
2022-11-16 17:34:31.9950 info    connector:shutdown_status :   final goroutine statuses:
2022-11-16 17:34:31.9950 info    connector:shutdown_status :     /connector/background-metriton: exited without error
2022-11-16 17:34:31.9950 info    connector:shutdown_status :     /connector/config-reload      : exited without error
2022-11-16 17:34:31.9950 info    connector:shutdown_status :     /connector/refresh-token      : exited with error
2022-11-16 17:34:31.9950 info    connector:shutdown_status :     /connector/server-grpc        : exited without error
2022-11-16 17:34:31.9950 info    connector:shutdown_status :     /connector/service            : exited without error
2022-11-16 17:34:31.9951 info    connector:shutdown_status :     /connector/session            : exited without error
2022-11-16 17:34:31.9951 error   lstat /Users/****/Library/Caches/telepresence: no such file or directory
telepresence: error: lstat /Users/****/Library/Caches/telepresence: no such file or directory

I've tried running the commands you suggested and it worked! Thank you.

[alexolivier]

I'm getting the same issue - killing the deamon still doesn't work.

Darwin MacBook-Pro.local 22.1.0 Darwin Kernel Version 22.1.0: Sun Oct  9 20:14:30 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T8103 arm64

[OscartGiles]

Same issue here. Also on M1 Mac.

[philipsabri]

Same issue here with M1 Mac

[roderik]

This works for me mkdir -p /Users/$USER/Library/Caches/telepresence

[jiangxiaoqiang]

mkdir -p /Users/$USER/Library/Caches/telepresence

I have tried this but did not work for me:

➜  dolphin-post git:(master) mkdir -p /Users/$USER/Library/Caches/telepresence
➜  dolphin-post git:(master) telepresence connect
Launching Telepresence Root Daemon
Need root privileges to run: /opt/homebrew/bin/telepresence daemon-foreground /Users/xiaoqiangjiang/Library/Logs/telepresence '/Users/xiaoqiangjiang/Library/Application Support/telepresence'
Password:
Launching Telepresence User Daemon
telepresence: error: connector service did not start: timeout while waiting for connector to start
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 .

[themiken]

This works for me mkdir -p /Users/$USER/Library/Caches/telepresence

This works for me too

[weiqiangxu]

这对我有用mkdir -p /Users/$USER/Library/Caches/telepresence

thanks

[opvexe]

mkdir -p /Users/$USER/Library/Caches/telepresence

It works for my M1

[thallgren]

The Helm install failed. You'll need to find out why. A kubectl -n ambassador get events shortly after the failure might be helpful. I'm closing this ticket because the original issue seems to have been resolved.

[nhaancs]

This works for me mkdir -p /Users/$USER/Library/Caches/telepresence

This works for me too, thank you.

[u2bo]

This works for me mkdir -p /Users/$USER/Library/Caches/telepresence

win11 path？