You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Up until v24.5.1 (inclusive) is was able to run nimbus-beacon-node on systemd with MemoryDenyWriteExecute=true. MemoryDenyWriteExecute is a systemd hardening feature that prohibits attempts to create memory mappings that are writable and executable at the same time.
Now, on v24.6.0, nimbus-beacon-node crashes with Failure in taskpool initialization when MemoryDenyWriteExecute is enabled. There are a few good reasons why you may need write and execute. Still, I am letting you know in case it was accidental.
Up until v24.5.1 (inclusive) is was able to run nimbus-beacon-node on systemd with
MemoryDenyWriteExecute=true
.MemoryDenyWriteExecute
is a systemd hardening feature that prohibits attempts to create memory mappings that are writable and executable at the same time.Now, on v24.6.0, nimbus-beacon-node crashes with
Failure in taskpool initialization
whenMemoryDenyWriteExecute
is enabled. There are a few good reasons why you may need write and execute. Still, I am letting you know in case it was accidental.Here's the full crash output:
Platform details (OS, architecture): Debian 12, amd64
nimbus installed from the
https://apt.status.im/nimbus
Debian repo.The text was updated successfully, but these errors were encountered: