Open Antyk1234 opened 3 years ago
hi @Antyk1234 , thank you for reporting, please give us some time to investigate
was it a fast synced node?
Yes, it was.
I've had four different nodes on different chains, including some run by colleagues, fail in this way. Nobody is pruning, everyone is using Fast Sync.
Glad to help debug this.
ETA versions in my cases are 1.10.77 and 1.9.54
I read the source, it appears to me that if the node has been disconnected from peers and sealing for longer than 1024 blocks it will fail to find a common ancestor. This is a fraction of a day on most chains. A better-chosen _ancestorJumps will address this.
@tkstanczak what is the status of this?
On Thursday on 22/07/2021 node stopped syncing. The latest block number is 10689829. Here is an example of logs after docker restart:
Os: Ubuntu 18.04.2 LTS Node version: latest