-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Can not sync pyrmont testnet #9450
Comments
#9452 Seems to resolve this issue. Keeping it open for a little while until we have more data. |
Waiting for confirmation from a node syncing from genesis. |
I have the same issue with command since 20.08: So I tried to use infura ETH1 provider instead But got the message:
Not sure what to do now. Thanks! |
After 2021-08-22 I got the same loop errors - no good blocks in batch. |
You definitely need 2.0.0 for pyrmont testnet after the altair fork. The errors of my node now changed after restarting it like 12h ago:
|
hey @iSOcH @tkachevaa , this will be patched in our next v2 release candidate. #9452 has the fix, our tentative time for our next release will be most likely at the start of next week. |
Now i got the same errors |
With v2.0.0-rc.1 problem was solved, synced and start to validate |
I tried to use
The data dir was empty. This is what I've got:
and it continues to be like that for the last 3 hours. |
So this is out of our control @pdyraga . Geth had a bug which broke blockhash computation for clique networks. You can either run your own updated geth node with the fix or wait till its an official release and infura updates its nodes with the fix. Alternatively, you can run with a |
I started my first testnet attempts 3 days ago and I kept receiving similar errors (beacon node doesn't have a parent in db with root: 0x...). I thought, if bugs like this is the norm, I should stay away. @nisdas thanks for the explanation. |
Can not sync pyrmont testnet post fork in a period of non finality. Node is stuck with:
Some evidence gathered so far:
Some targets to consider:
The text was updated successfully, but these errors were encountered: