-
-
Notifications
You must be signed in to change notification settings - Fork 266
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
Error updating eth1 chain cache message=Invalid length index (kintsugi-lodestar-geth/nethermind) #3597
Comments
Interesting... haven't seen this one before @g11tech. |
@SeaMonkey82 is this coming now/reproducible? couldn't find this in the log of the recently updated kintsugi nodes @philknows seems like deposit data is not correct, not a kintsugi issue though, but could be because of bad blocks that are being pushed into network as part of robustness/stress testing. |
edit Different error now.
|
this error looks legit, as the attestation arrive for a future slot it seems as we currently reject future slot attestation/arriving early than expected. |
|
Hi @SeaMonkey82 Since am not able to see this on our nodes. Could you help me with these? 🙂 |
Occurs consistently. Here is the log from lodestar-geth. lodestar-nethermind looks similar.
|
@SeaMonkey82 thanks! 🙂 I will try to repro at my end. I am not that worried about invalid attestation as an attestation could potentially arrive earlier than block causing this error (but I will still try validating if this is the case). In future lodestar could queue this attestation up to process later. However I am more curious about the reasons behind |
Update: This error was caused by including Leaving this issue open in case of any further discussion or action. It seems to me that |
Thanks @SeaMonkey82 . Yes, the validator does validate the config it fetches from beacon against its own config.yaml. will check it out why it hasn't happened here. |
I guess the fact that these messages stopped after restarting my validators without |
I also saw this on my first run of
This was reproducible after wiping the data directory and re-running. I suspect there's a bad interaction between Lodestar/Nethermind, because after switching the order of eth1 providers (presumably to give Erigon priority over Nethermind) the problem went away. (Although I then encounter #3550 and something to do with FWIW, I have Nethermind using their recommended configuration for validators: |
thank you for the update! so it seems that it has nothing to do with the kintsugi/bellatrix but deposit tracker interaction with the EL. let me try to replicate using the nethermind master |
Could you provide nethermind branch + commit /docker image details along with the (exact if possible) command that you used to spin up nethermind? UPDATE: I was able to run lodestar on prater with eth1 as nethermind without any issue:
nethermind args: |
Et voila! This annoying error is now RESOLVED!!! 🥳 And you @blampe seems to have mixed up the networks on CL and EL side, so this error could again comeup because of wrong/unexpected feed of the deposit roots resulting again to the scenario described above! Anyway, now one doesn't need to worry about configuration, kintsugi configuration can now automatically be loaded with cc: @philknows "repro-ing" this error was harder than solving it 🤣 special thanks to Nethermind's @MarekM25 and his teammate @AntiD2ta for helping repro this error! |
Describe the bug
Flood of this error
Error updating eth1 chain cache message=Invalid length index
Expected behavior
non-error output
Steps to Reproduce
Sync kintsugi-lodestar-geth or kintsugi-lodestar-nethermind (maybe all EL clients?)
ScreenshotsOutputDesktop (please complete the following information):
The text was updated successfully, but these errors were encountered: