-
Notifications
You must be signed in to change notification settings - Fork 80
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
com.apple.launchd.peruser.501[247]: (meshagent[31372]) Job appears to have crashed: Abort trap: 6 #5
Comments
I'll take a look at this, as I actually saw this exact same crash on my machine earlier today when the agent performed a self update. |
I just installed it, it never showed up in the web interface. |
How can I install an older client to confirm it's the update? |
FYI. You can run the mesh agent manually by typing "./meshagent run" from the command line. This is helpful for debugging. For versioning, the agent just runs a self-hash on itself and sends it to the server. If the hash does not match the server's version, update is initiated. You can look at the file size of the agent. One trick is to append a single byte to the agent and run it again, it will cause an update. |
That sounds like an the upgrade, not how to downgrade. Or do I just have to downgrade the server and trigger that check again? I would like to check that it did work with an older version, i.e. to pin down the breaking version, and it is not because of my rather old system (Mac OS 10.9.5) I'm on. Or has @krayon007 already enough found something? |
Any updates on this? |
I've fixed a few things related to crashes. Not sure which one specifically you saw. I haven't been able to reproduce this lately tho. |
So to test, I update mesh central to the latest version, and download the client from there? Edit: With it updated to |
I made a backup of the Here is the result: mac:~ luckydonald$ /usr/local/mesh_services/meshagent/meshagent_osx64.bak
MeshCentral2 Agent
Unable to open database (1/10)...
Segmentation fault: 11 Edit: "Unable to open database" might be related to #9? |
Creating new issue, #10, as the original thing doesn't seem to happen anymore. |
The text was updated successfully, but these errors were encountered: