-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
EXC_BAD_ACCESS (Code Signature Invalid) on M1 #2217
Comments
This seems relevant: https://stackoverflow.com/a/41868747 |
Same with version 1.3.1 and MacOS Monterey 12.2.1: ./node_exporter --version
Killed: 9
codesign -v node_exporter
node_exporter: invalid signature (code or signature have been modified)
In architecture: arm64 |
Actually I guess this is expected given that we don't sign the code. Can you try https://github.molgen.mpg.de/pages/bs/macOSnotes/mac/mac_procs_unsigned.html |
I've tried and I got the same result. I don't think that is because the binary is not signed, for example on Mac x86_64 it works: ./node_exporter --version
node_exporter, version 1.3.1 (branch: HEAD, revision: a2321e7b940ddcff26873612bccdf7cd4c42b6b6)
build user: root@6da4230b7124
build date: 20211205-11:13:08
go version: go1.17.3
platform: darwin/amd64
codesign -vvv node_exporter
node_exporter: code object is not signed at all
In architecture: x86_64 But this is MacOS 11.4. You can see the difference, here |
the workaround that worked for me:
|
Host operating system: output of
uname -a
Darwin m1minimatto01 20.6.0 Darwin Kernel Version 20.6.0: Tue Oct 12 18:33:38 PDT 2021; root:xnu-7195.141.8~1/RELEASE_ARM64_T8101 arm64
node_exporter version: output of
node_exporter --version
1.3.0
node_exporter command line flags
N/A
Are you running node_exporter in Docker?
No.
What did you do that produced an error?
./node_exporter --version
What did you expect to see?
normal process startup
What did you see instead?
zsh: killed ./node_exporter --version
From ~/Library/Logs/DiagnosticReports/node_exporter_2021-11-24-183421_m1minimatto01.crash:
The text was updated successfully, but these errors were encountered: