go-ethereum

go-ethereum copied to clipboard

System information

Geth version: v1.10.25 CL client & version: [email protected] OS & Version: Docker on Linux

Expected behaviour

No error entry in logs

Actual behaviour

Every minute I've got this entry in my logs :

{"err":"block receipts missing, can't freeze block 15540785","lvl":"eror","msg":"Error in block freeze operation","t":"2022-10-01T09:38:42.233700369Z"}

It's looks like issue #20239 but on block 15540785 on the main net.

Hi,

I have similar error : ERROR[10-18|12:49:01.737] Error in block freeze operation err="block receipts missing, can't freeze block 15578290

When did you do the initial sync with your nodes? Do you have a log containing Loaded last fast-sync pivot marker that you could share?

Initial sync was made early September. For your log entry I have this :

{"lvl":"info","msg":"Loaded last fast-sync pivot marker","number":15753187,"t":"2022-10-28T21:36:04.705328393Z"}

did you use kill -9 to stop geth(forced)?

did you use kill -9 to stop geth(forced)?

Unfortunately Docker do it for me when updating

How can you get out of this situation?

Can I fix the error block manually?

geth.log

Got these from a friend

Same issue, Error in block freeze operation, err="block receipts missing, can't freeze block 16433980”

Geth version: v1.10.26

Can it be resolved without resync?

Update: Loaded last fast-sync pivot marker: number=16,440,307

did you use kill -9 to stop geth(forced)?

Unfortunately Docker do it for me when updating

If you are using Docker, make sure to set the stop_grace_period to like 3m. Docker's default stop grace period is 10s, which is way to short for a clean geth stop

If you are using Docker, make sure to set the stop_grace_period to like 3m. Docker's default stop grace period is 10s, which is way to short for a clean geth stop

Not working when using Swarm : https://github.com/moby/moby/issues/36955

did you use kill -9 to stop geth(forced)?

@hotcoin-walle FWIW I can confirm that's definitely what happened to me, I didn't gracefully shutdown the node

I saw this on a friend's holesky node today.

Error in block freeze operation          err="block receipts missing, can't freeze block 1"

They were running from genesis. Unfortunately did not still have the logs from around when the client started, but did state the machine was choked at the beginning and fell behind before the chain cooled off and they were able to catch back up.