-
Notifications
You must be signed in to change notification settings - Fork 754
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: Failed to update deposit cache #4495
Comments
Workaround while investigation continues: |
for additional context, LH requests the deposit contract logs in 1000 block ranges. The error implies that the logs in the given range are not in strictly increasing order. From past experience, this usually means that the EL is missing a few logs in that range |
teku nodes with this issue showing |
Restarting besu (and deleting the caches/ dir) and restarting teku/lighthouse has resolved the problem for everyone I've seen so far. |
restarted with passing |
looking at etherscan, there seems to be an indexing anomaly there too
|
450831 is 06E10F in hex and 0FE106 in little endian - which matches the "index" of the log in etherscan |
The current working theory is that when a re-org happens the logs bloom cache is not updated correctly. We are attempting to reproduce in test code. |
I'm having the same problem with Lighthouse 3.1.2, Besu 22.7.4. I know how to stop/start Besu, but how exactly do you "delete the caches/ folder under besu's data directory" with the terminal only? Thanks |
@lincoln2020 sorry for late reply
command to delete would be |
Reported in Discord
Lighthouse v3.1.2-01e84b7
Besu v22.7.5
Oct 07 03:44:05.686 ERRO Error updating deposit contract cache error: Failed to update deposit cache: "FailedToInsertDeposit(NonConsecutive { log_index: 450832, expected: 450831 })", retry_millis: 60000, service: deposit_contract_rpc
We (Protocols) are also seeing this on some Besu/Teku nodes that we run. at least one is running Besu 22.7.2
The text was updated successfully, but these errors were encountered: