Can bad blocks stop synchronization from working?

[AsadullahSoomro]

I encountered these errors during synchronization:

• Warning: "Downloader queue stats"
• Warning: "Sync Failed, Dropping Peer"
• Error: "Retrieved hash chain is invalid: no peers available or all tried for download"
• Error: "Peer is unknown or unhealthy"
• Error: "Timeout"
• Error: "Pending request exists for joining peer"
• Error: "Expired request does not exist"

However, after some time(approximately 20 hours), the new node started working fine,

[rjl493456442]

bad blocks stop synchronization from working

No, geth should be capable to identify the bad block, throw it away and follow the chain guided by the consensus client.

no peers available or all tried for download

Are you running some Non-Pos network? IIRC, this kind of error shouldn't show up after switching to Proof-of-stake

[AsadullahSoomro]

I am using Clique PoA(Proof-of-Athuority) Consensus algorithm.

…

On Tue, Apr 30, 2024, 13:15 rjl493456442 ***@***.***> wrote: bad blocks stop synchronization from working No, geth should be capable to identify the bad block, throw it away and follow the chain guided by the consensus client. no peers available or all tried for download Are you running some Non-Pos network? IIRC, this kind of error shouldn't show up after switching to Proof-of-stake — Reply to this email directly, view it on GitHub <#29685 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALDJT4QOQLYX7M7DF7AFSATY75HLTAVCNFSM6AAAAABG7UO2VGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBUGY3TKMRZGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[rjl493456442]

Which network you are trying to sync. Keep in mind that Rinkeby and Goerli has been deprecated.

[AsadullahSoomro]

@rjl493456442 I am using Clique PoA(Proof-of-Athuority) Consensus algorithm.