Sync failed with error: no peers available or all tried for download #1830
Description
System information
Geth version: both v1.2.9 & v1.2.10
OS & Version: Linux
Commit hash : 2b83693
Expected behaviour
The node was lagging behind for several days, when restarted, the node tries to catch up to the latest block.
It should succeed.
Actual behaviour
The node will print logs like bellow and got stuck, restart can not help.
t=2023-08-17T13:04:18+0000 lvl=warn msg="Synchronisation failed, dropping peer" peer=9fdfe7c27c400df9086f711755aa4445b379038a617e6173bd2c8b24b8393e63 err="retrieved hash chain is invalid: no peers available or all tried for download"
t=2023-08-17T13:04:26+0000 lvl=warn msg="Synchronisation failed, dropping peer" peer=dca345bdef989c40b4584d2a48cd8a16a8590185b8515fbfa6d1f5d21afb122b err="retrieved hash chain is invalid: no peers available or all tried for download"
t=2023-08-17T13:04:33+0000 lvl=warn msg="Synchronisation failed, dropping peer" peer=c22284eec0f51db6569bcfbff26a7e32483472f8300f6f544e00148e3f9b1e19 err="retrieved hash chain is invalid: no peers available or all tried for download"
t=2023-08-17T13:04:41+0000 lvl=warn msg="Synchronisation failed, dropping peer" peer=1b59f42e85f0a4da833f5de1870063ead04991200fb5b94292c0f103fd68d20f err="retrieved hash chain is invalid: no peers available or all tried for download"
Steps to reproduce the behaviour
Shutdown your node for 1 day, then restart it. It would connect to some nodes and download a few block headers, then it got stuck. Always got stuck at same height.
Backtrace
NA