Closed sduchesneau closed 9 months ago
Fixed in tag bsc-v1.2.10-fh2.2-2
It seems that this happens again (few reports from Pinax and others)
example here:
0034137009-7d207ab4581d763b-c4b878e229f8e968-34137006-default.dbin.zst
0034137009-d6eb576e901cca43-c4b878e229f8e968-34137007-default.dbin.zst
0034137010-039cb3ec9248b76b-d6eb576e901cca43-34137007-default.dbin.zst
0034137010-1b111828d2da7d08-7d207ab4581d763b-34137007-default.dbin.zst
0034137011-d6a759593ed7a8f5-1b111828d2da7d08-34137008-default.dbin.zst
^this is problematic because the correct path is:
we are missing the previous files to figure out the root cause. The 7009 block links to 7006, but there was probably another block that set the wrong "last final block" before that.
Fixed in https://github.com/streamingfast/go-ethereum/releases/tag/bsc-v1.3.7-fh2.2-1 The "final block num" will not be advertised anymore if the block being written by geth is not canonical.
Finality was shown as
31045129
on RPC call:but according to our instrumnentation, it was stuck at
31042249
This '31042249' issue has been observed on multiple unrelated machines running bsc-v1.2.10-fh2.2
It solved itself at block
31045554