-
-
Notifications
You must be signed in to change notification settings - Fork 265
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
beaconchain sync stuck on mainnet, pyrmont, and prater #2949
Comments
Similar issue with Pyrmont actually. :(
|
Mainnet ....
|
Ok, I was resetting the databases and did fresh sync on all networks and they get stuck on the very same blocks again:
|
Thanks for reporting! Could you dump here the debug logs? If block processing of sync blocks fails it will be visible there |
I think I already identified it:
|
Oh damn! I wonder how is that possible, given that we pass specs tests. @tuyennhv Could you take a look?
|
Describe the bug
Lodestar 0.28 does not sync Prater testnet. It get's stuck on epoch 126 / head https://prater.beaconcha.in/block/4095
Expected behavior
Lodestar 0.28 does sync Prater testnet. ;)
Steps to Reproduce
Screenshots
Desktop (please complete the following information):
kernel 5.10.11-arch1-1 #1 SMP PREEMPT Wed, 27 Jan 2021 13:53:16 +0000 x86_64 GNU/Linux
v0.28.0
master
nvm use lts/fermium
/Now using node v14.17.4 (npm v7.20.5)
The text was updated successfully, but these errors were encountered: