-
-
Notifications
You must be signed in to change notification settings - Fork 516
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
Root Daemon: Not running #3551
Comments
Is this amd64 or arm64 (M1)? |
M1. $ arch
arm64
$ file `which telepresence`
/Users/paul/bin/telepresence: Mach-O 64-bit executable arm64 |
I did some debugging, and it turns out that In my case, the error is "daemon service did not start: timeout while waiting for daemon to start", which unfortunately does not tell us anything new. |
So, it turns out that this system has Apparently |
Alright, to wrap this all up: if I manually start the root daemon with sudo before running |
Thanks for the info. Any ideas on how we can improve how this is handled in Telepresence? |
I think not hiding the error is a good start (#3559), but I'm not sure if the underlying problem can be solved completely. Maybe Another possibility (which I've not extensively tested) might be to run |
It looks like the error display has been addressed. I'll leave this open as a feature request for the process check suggestions. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment, or this will be closed in 7 days. |
Describe the bug
The telepresence root daemon does not start. The daemon.log file is empty.
To Reproduce
telepresence connect
. It tells me it needs root privileges, which I provide:telepresence status
, observe that root daemon is not runningI don't see the daemon-foreground in ps output. When I run it manually it doesn't seem to crash (and writes a startup message to
daemon.log
), buttelepresence status
still reports 'not running'. It does create a/var/run/telepresence-daemon.socket
.Expected behavior
A clear and concise description of what you expected to happen.
Versions (please complete the following information):
macOS Sonoma 14.4.1 (23E224)
Additional context
It appears as if this issue started happening after upgrading to macOS Sonoma 14.4.1.
daemon.log
The text was updated successfully, but these errors were encountered: