EXC_BAD_ACCESS (Code Signature Invalid) on M1

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:

Path:                  /private/var/tmp/*/node_exporter
Identifier:            node_exporter
Version:               ???
Code Type:             ARM-64 (Native)
Parent Process:        zsh [66552]
User ID:               501

Date/Time:             2021-11-24 18:34:13.890 -0800
OS Version:            macOS 11.6.1 (20G224)
Report Version:        12
Anonymous UUID:        1402C51B-C2D2-3335-DB7D-371D75A460F2

Sleep/Wake UUID:       0278B6A8-868D-4234-BA26-521B35406C0D

Time Awake Since Boot: 160000 seconds
Time Since Wake:       38000 seconds

System Integrity Protection: enabled

Crashed Thread:        Unknown

Exception Type:        EXC_BAD_ACCESS (Code Signature Invalid)
Exception Codes:       0x0000000000000032, 0x00000001005f4000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace CODESIGNING, Code 0x2

Reproduce the failure with ./node_exporter --version on the reported M1 macOS environment and compare it with the supplied crash report. The issue is resolved when node_exporter starts normally instead of being terminated with EXC_BAD_ACCESS (Code Signature Invalid).