🐞 Bug Report
I am running v2.1.4 of beaconchain and validator. The validator can't proceed because the beaconchain is not syncing properly.
A clear and concise description of the problem...
On restart of the beaconchain, it seems to be stuck trying to complete the initial-sync portion. It keeps repeating this in the log:
Aug 20 09:29:58 nuc4 beacon-chain: time="2022-08-20 09:29:58" level=info msg="Connected to new endpoint: http://localhost:8551" prefix=powchain
Aug 20 09:30:05 nuc4 beacon-chain: time="2022-08-20 09:30:05" level=info msg="Processing block batch of size 57 starting from 0x99d6671e... 3707969/3708750 - estimated time remaining 4m34s" blocksPerSecond=2.9 peers=45 prefix=initial-sync
Aug 20 09:30:05 nuc4 beacon-chain: time="2022-08-20 09:30:05" level=warning msg="Batch is not processed" error="could not process block in batch: could not process block: could not process block header: parent root 0x5e918c1757a5ae990d67d869f909a344199fe5e0448999782049e5bdf382eb18 does not match the latest block header signing root in state 0x9ef78c510be027cb8abebfe3910c4a3b82f21ce5446d9c541903b7ba25398369" prefix=initial-sync
Aug 20 09:30:05 nuc4 beacon-chain: time="2022-08-20 09:30:05" level=info msg="Processing block batch of size 58 starting from 0x90aa636a... 3708033/3708750 - estimated time remaining 2m4s" blocksPerSecond=5.8 peers=45 prefix=initial-sync
Aug 20 09:30:06 nuc4 beacon-chain: time="2022-08-20 09:30:06" level=error msg="Could not get reconstruct full bellatrix block from blinded body" error="could not fetch execution block with txs by hash 0x01d1075f83868e6eb900e4e255d83903d0c869748e858f2b809500f9d563c204: timeout from http.Client" prefix=sync
(see attached for the complete log fragment)
This seems similar to another issue with the same title - but that was for ropsten, but this one is for praeter/goerli. Maybe I should have combined issues? (Maybe the same issue as https://github.com/prysmaticlabs/prysm/issues/11270)
Has this worked before in a previous version?
Yes, the previous version in which this bug was not present was: ....
Yes, this was working before. I was using 2.1.4-rc1 going into the merge. Last night, I stopped and restarted and from there, it kept repeating this in the log. I upgraded to 2.1.4 but it did not improve the situation.
🔬 Minimal Reproduction
🌍 Your Environment
VERSION="20.04.4 LTS (Focal Fossa)"
What version of Prysm are you running? (Which release)
Anything else relevant (validator index / public key)?
$ geth version
Git Commit: 671094279e8d27f4b4c3c94bf8b636c26b473976
Go Version: go1.18.4
Operating System: linux
geth --goerli --http --cache=2048 --datadir --http.api eth,net,engine,admin --authrpc.vhosts="localhost" --authrpc.jwtsecret=/jwt.hex
/usr/local/bin/beacon-chain --datadir= --http-web3provider=http://localhost:8551 --prater --jwt-secret=/jwt.hex --genesis-state=/genesis.ssz --accept-terms-of-use --suggested-fee-recipient=0x