-
Notifications
You must be signed in to change notification settings - Fork 141
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
fatal error: index out of range #626
Comments
Thanks for the reporting. Have you started a fresh sync or it happened on long running nodes? We will try to reproduce it and report back. |
It seems to come back even after fresh syncs. It's in snap sync mode. Start file
And config toml
I think it maybe has something to do with running in a container. But of course could also be some hardware fault on my pc. |
We were still not able to reproduce. We will try again using the config you give above.
|
I tested snap sync on 3 different machines using the v1.12.19 and your provided TOML config file and went smooth. Probably it has to do with the proxmox lxc containers. If you provide more info on how to setup the same config, I will try to reproduce it. |
I am running a few etc nodes in proxmox lxc containers on a minisforum um480 and they all seem to fail with the same error at some point. Already checked ram wit memtest even replace ram resynced database but it keeps happening.
Core-geth version is latest release.
I wonder if it has to do with the chain reorg detected a few times before the crash.
The text was updated successfully, but these errors were encountered: