-
Notifications
You must be signed in to change notification settings - Fork 62
-
Notifications
You must be signed in to change notification settings - Fork 62
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
[ML] macOS: Controller process sometimes terminated with SIGKILL #2429
Comments
The error re-appeared randomly on development machine (perhaps the ES build system downloaded new binaries?) I was able to test resigning the app with an ad hoc signature and found that it does stop the app being killed when started.
From the
|
Almost exactly 1 year later this problem has returned. The easiest way to resolve the problem is still to delete
|
Some developers working in the Elasticsearch repository have reported intermittent problems with the machine learning controller process crashing when running a locally built Elasticsearch. The usual symptoms are Elasticsearch will fail to start and the log will contain this message:
A crash report can be found in the macOS Console app.
The error has been observed on Apple silicon only (so far).
Reproducing
It has not been possible to reproduce reliably but once the problem occurs a crash report can be generated by running
controller --help
in the Elasticsearch repository.Running the app from a different location works ?!
Copy the app to a folder in the home directory and running the copy does not result in a crash:
Possible Causes
macOS Quarantine
No.
The downloaded
controller.app
does not have the the quarantine attribute set.find . -xattrname com.apple.quarantine
returns nothing.Security Policy
No.
After disabling security with
sudo spctl --global-disable
the controller app still crashes.When security is enabled the
spctl --assess
function returns the same message ascodesign --verify
Code Signing
Maybe.
The crash report indicates code signing is involved
and
Verifying the signing returns an error message
It is not clear if that is a terminal error however.
Workarounds
In the commands below replace
elasticsearch-8.7.0-SNAPSHOT
with your version.The text was updated successfully, but these errors were encountered: