Skip to content
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

Failed proposal: invalid eth-consensus-block-value header #1914

Open
olegshmuelov opened this issue Dec 4, 2024 · 1 comment
Open

Failed proposal: invalid eth-consensus-block-value header #1914

olegshmuelov opened this issue Dec 4, 2024 · 1 comment
Assignees
Labels
bug Something isn't working on hold

Comments

@olegshmuelov
Copy link
Contributor

The following error occurred during proposal processing:

failed to get proposal: proposal header Eth-Consensus-Block-Value not a valid integer

This issue could potentially be related to a beacon node (BN) or go-eth2-client. Further investigation is required to confirm the root cause.

Occurred on stage cluster 275-278 v2.0.1

@olegshmuelov olegshmuelov added the bug Something isn't working label Dec 4, 2024
@anatolie-ssv anatolie-ssv self-assigned this Dec 18, 2024
@anatolie-ssv
Copy link
Contributor

After inspecting go-eth2-client and prysm code it seems that the error is on the prysm side when it's trying to get the block value but fails with an internal server error, then sets the mentioned header to empty string, which in turn causes the eth2 client to fail when trying to cast it to an int:

https://github.com/prysmaticlabs/prysm/blob/develop/beacon-chain/rpc/eth/validator/handlers_block.go...

Because the logs containing these errors (in stage) are no longer accessible, this task will be put on hold. The logs are important because there are 3 cases when prysm fails to get the block and in all cases it will log the cause before setting the value of the header to "".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working on hold
Projects
None yet
Development

No branches or pull requests

2 participants