-
Notifications
You must be signed in to change notification settings - Fork 13
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 to request signed beacon block #41
Comments
Hey! I think this is just an incompatibility with Prysm - nothing on your side. I'll have a look in to it and see what the best option is. Thanks for the issue! |
I also still see this with prysm 3.1.1 |
Should be fixed when prysmaticlabs/prysm#11666 is released 👌 |
That would be great, will keep an eye out when next Prysm release is out, thanks! |
Just updated Prysm to latest release v3.2.0 which includes: And updated ethereum-metrics-exporter to latest release v0.19.0 Getting these messages ending with some errors at the end of the log;
and then keeps repeating this message:
|
Same issue with the same version of Prysm. Even if this is an issue with prysm doing something non-standard, is it possible for ethereum-metrics-exporter to gracefully handle this and still export the rest of the data? |
Hi, so this was merged in https://github.com/prysmaticlabs/prysm/releases/tag/v3.2.0 If I try, I an sucessfully subscribe
I figure this is where the log output is produced: But I cannot quite figure out why |
Hi,
Trying out this awesome exporter with Prometheus and Grafana and got it working, but still see an error in the logs.
Using Geth (latest) for EL and Prysm (latest) for CL.
The error in the logs show this:
ethereum-metrics-exporter[25186]: {"component":"exporter","error":"failed to request signed beacon block: GET failed with status 500: {\"message\":\"GetBlockV2: rpc error: code = NotFound desc = Could not find requested block: signed beac on block can't be nil\",\"code\":500}","level":"error","module":"consensus/beacon","msg":"Subscriber error","time":"2022-08-01T11:21:00+02:00","topic":"block"}
Is this a misconfiguration from my side or could it be something else?
Flags used:
--consensus-url=http://localhost:3500 --execution-url=http://localhost:8545
Prysm public API: https://docs.prylabs.network/docs/how-prysm-works/prysm-public-api
The text was updated successfully, but these errors were encountered: