-
Notifications
You must be signed in to change notification settings - Fork 375
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
bad optional access
error at startup
#1334
Comments
bad optional access
error at startup
hey thanks for reporting
This is a known issue when trim_headers and prune are used together, and will be fixed by #1270 in the next release I think you have enough memory to switch off trim_headers which should resolve your issue |
is there a known date for the next release that includes this fix? |
@rachyandco not yet, but the release candidate is in testing if you'd like to use that for now it's likely to be the same as the release version https://github.com/delta1/elements-guix-build/releases/tag/elements-23.2.2rc2 |
This issue can be closed, the fix for trim_headers works and we upgraded BTCPay elementsd image to 23.2.3 and it works again. Thank you very much for the fix. |
Fix included in 23.2.2 and upwards https://github.com/ElementsProject/elements/releases |
Elementsd is at "Pruning blockstore" and shutdown after a
EXCEPTION: St19bad_optional_access
orbad optional access
error at startup.Expected behavior
Node should sync.
Actual behavior
Fails at prunning blockstore and reboots.
To reproduce
This is an elemenstd running inside a docker within a BTCPayServer setup. The following instruction were done btcpayserver/btcpayserver#1282
System information
ubuntu 22.04, Docker version 26.1.3, build b72abbb
v23.2.1 inside a docker.
VPS with 32G mem, 4G swap, 8 core machine with more than 100G free disk space.
logs:
The text was updated successfully, but these errors were encountered: