-
Notifications
You must be signed in to change notification settings - Fork 951
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to retrieve proof-of-stake genesis block data #12497
Comments
I have the same issue, this happens to me when the timestamp in the genesis file of geth and the timestamp of the genesis state of prysm are not equal. |
@Fueav @aaroua5 You can try our latest devnet instructions, this should fix this issue |
@nisdas I updated the beacon-chain startup command, but the problem was not solved. As for the error logs of the genesis node, it seems to be a network issue that caused a delay in the synchronization of p2p information. However, I am sure that I have synchronized the time according to timedatectl. |
@Fueav It means your node is syncing, you will have to wait for it to be fully synced |
I don't think so, because I noticed that the sync_distance is 0. |
No, the logs in indicate your execution client is still syncing. So wait for that to finish syncing first. If |
@nisdas In fact, I once maintained this state for more than 12 hours. The situation did not improve and there were not many blocks in the devnet, which quickly caught up with the footsteps of the genesis node. |
Maybe you should look at your execution logs in that case @Fueav , it would indicate what the issue is |
@nisdas geth seems to be synchronizing blocks through fork choice, the only thing worth noting is this warning log. |
Looks like it has no peers @Fueav , it maybe better to do a full sync. |
@nisdas geth is already --syncmode=full |
You can give that a try, our devnet instructions are only for 1 node currently. If you need to add multiple nodes, then you will have to configure a geth/execution bootnode. |
I tried, but it didn't work.v4.0.3 running normally, and I'm ready to revert back to this version. |
Any progress? Many... many issues mainly involving sync
and
|
@icemagno I encountered the same error. How did you resolve it? |
@Fueav , @lyfsn , @nisdas |
@Gopal-Gurram same issue, trying to add another node to this proof of stake devnet setup and if fails to sync. Did you resolve your issue? |
no @netoneko |
@lyfsn I've started to use Hyperledger Besu. You can check my old try anyway... May the force be with you in this path |
Closing old issues. This seems like a devnet setup issue rather than a Prysm issue. Please file again with reproduction steps if this is still an issue. |
馃悶 Bug Report
Description
I'm building my devnet creation node to block normally, and other nodes have encountered problems when joining.
Has this worked before in a previous version?
Yes, the previous version in which this bug was not present was: ....馃敩 Minimal Reproduction
馃敟 Error
馃實 Your Environment
Operating System:
What version of Prysm are you running? (Which release)
Anything else relevant (validator index / public key)?
The text was updated successfully, but these errors were encountered: