-
Notifications
You must be signed in to change notification settings - Fork 496
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
MacOS 13: MeshAgent service disappears after reboot #4822
Comments
This is happening for me as well on an Intel Mac running 13.0.1. All seems good if I run |
In my case systemctl doesn't exist but I was able to do the same thing with launchctl. On an M1 system the command was: sudo launchctl load /Library/LaunchDaemons/meshagent_osx64_LaunchDaemon.plist Confirmed that it brings the service back to life. Unfortunately it doesn't help it survive a reboot. Suggestions? |
+1 for me too on M1 system and Ventura 13.2 |
+1 here. |
I may have found a solution to this. If you run:
Exit and save the file and then restart the computer and the Mesh Agent should load. |
@superbam Perfect - worked for me! Thanks! |
@superbam this also fixed my issue. my meshagent was named different meshagent_osx64... as long as i made the changes it boots perfectly. Thx |
This works. But I am getting blank screen on the Login page. I needed to login to make the screen available. Do anyone know why? |
Hi @AymanAnsari i guess the mac screen is black in reality too? So the mac is "sleeping". You have to wake up before login in desktop. |
No. it is not black in reality. As from other remote agent I can see the screen and connect. But only on Mesh it is showing this issue. |
I have this same symptom and i have spent time looking at the plist files running processes etc I have discovered that a funny symptom is that you have to manually log into the MacOS as a user - after that you can connect with meshagent, do everything normally (after adding the right permssions for Screen Recording and Accessibility) Im not sure how everything works but one thing I noticed is that It has to have 2 processes running - the standard one that is under "LaunchDaemons" and the kvm one that is under "LaunchAgents". I also had to do the mentioned naming fix. It seems that both having the same label makes agent not start. I got some good inspiration from another similar remote desktop related project - it describes how it is setup. Its experimental and doesnt work for me at all, but I got some some ideas from there Basically before login there should be something running as "meshagent -kvm1" but after successful login locally or with mac vnc remote management it is terminated and becomes meshagent -kvm0 running as user1 for example If the user logs out, it becomes meshagent -kvm1 again. I think there might be some permission issues or naming issues.
|
just an update for people. ive found the issue, from launchd.info EDIT: the issue/fix was actually here just didnt spot it! Ylianst/MeshAgent#161 |
Plz can people try the pkg in 1.1.22 which has bug fixes now |
MeshCentral 1.1.0, MacOS 13.0.1 on M1 Pro
After installing the MeshAgent the service will run and connect but disappear after a reboot. Service can be run manually to reconnect the computer but will not survive a reboot.
Both agents for MacOS exhibit this behavior
The text was updated successfully, but these errors were encountered: