Ethereum peer removal failed peer=-------- err="peer not registered"

[nilampatel-engineer]

bsc node has downloaded snapshot and now syncing from chain after a while suddenly started showing above error, can some one help pls

[Undead8]

I don't know what the error mean, but it's normal. It shows up all the time and it doesn't mean anything is wrong.

[nilampatel-engineer]

but the syncing has stopped from last few hours...

[Undead8]

Probably not related to that error.

[RumeelHussainbnb]

Can you please share the logs and please check its simillar to your issue it might be solve your problem https://github.com/ethereum/go-ethereum/issues/22077 if not please proceed to join our Discord channel for more discussion at https://discord.com/invite/binancesmartchain

[tculig]

I'm having the same issue where it says "Ethereum peer removal failed" and the sync just stops dead.

[forcodedancing]

@nilampatel-engineer @tculig We think this could be a potential bug, and we will look into it. Are your nodes recovered? If not, please let us know if we can help. Thanks.

[forcodedancing]

Linked to #220

[nilampatel-engineer]

@forcodedancing no node is not recovered, still same issue

[tculig]

My node recovered, thank you @forcodedancing. Took about 20 restarts, but in the end it managed to pull the entire history. Still importing block entries though, can't get it to fully sync. But that's a topic for another thread..

[nilampatel-engineer]

My node recovered, thank you @forcodedancing. Took about 20 restarts, but in the end it managed to pull the entire history. Still importing block entries though, can't get it to fully sync. But that's a topic for another thread..

how did you resolved?

[tculig]

My node recovered, thank you @forcodedancing. Took about 20 restarts, but in the end it managed to pull the entire history. Still importing block entries though, can't get it to fully sync. But that's a topic for another thread..

how did you resolved?

Just kept restarting the node whenever it crashed :/

[nilampatel-engineer]

I have snapshot downloaded and it is crashing on whem chain start syncing and giving me this error about peer removal failed

Get Outlook for Androidhttps://aka.ms/AAb9ysg

---

From: Slashy @.> Sent: Wednesday, January 12, 2022 12:26:22 PM To: binance-chain/bsc @.> Cc: nilampatel-engineer @.>; Mention @.> Subject: Re: [binance-chain/bsc] Ethereum peer removal failed peer=-------- err="peer not registered" (Issue #670)

My node recovered, thank you @forcodedancinghttps://github.com/forcodedancing. Took about 20 restarts, but in the end it managed to pull the entire history. Still importing block entries though, can't get it to fully sync. But that's a topic for another thread..

how did you resolved?

Just kept restarting the node whenever it crashed :/

— Reply to this email directly, view it on GitHubhttps://github.com/binance-chain/bsc/issues/670#issuecomment-1010994445, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATHSSIW77UNJVM5T7LNTMKTUVVXO5ANCNFSM5KGI32YQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.***>

[namlt3820]

Same problem here. I got it after pruning the snapshot. Now I have to manually check and restart the node everyday. My other node without any pruning is running just fine.

[ghost]

@forcodedancing Any update on this? My node keeps dropping blocks because of the above issue

[White-Rabbit-7]

I am having this exact same issue constantly.

ERROR[03-09|03:52:05.913] Ethereum peer removal failed peer=7946a12b err="peer not registered"

[KyloYang888]

I am having this exact same issue constantly.Now 100,000 blocks behind the main network because of this error

t=2022-03-10T03:38:59+0000 lvl=warn msg="Synchronisation failed, dropping peer" peer=570daaa966a5a500cbe0c41d985a49550e5e65fab99fa57eccea30989a1cff02 err=timeout
t=2022-03-10T03:38:59+0000 lvl=eror msg="Ethereum peer removal failed"          peer=570daaa9 err="peer not registered"

[lpf763827726]

same issue

t=2022-03-30T04:06:33+0000 lvl=info msg="Downloader queue stats"                 receiptTasks=0 blockTasks=380 itemSize="4.45 KiB" throttle=8192
t=2022-03-30T04:06:38+0000 lvl=eror msg="Snapshot extension registration failed" peer=51071016 err="peer connected on snap without compatible eth support"
t=2022-03-30T04:07:12+0000 lvl=eror msg="Ethereum peer removal failed"           peer=d3ff2bcb err="peer not registered"

[taweesakpintakam]

เมื่อ 30 มี.ค. 2022 11:07 "DouCrazy" @.***> เขียนว่า

same issue

t=2022-03-30T04:06:33+0000 lvl=info msg="Downloader queue stats" receiptTasks=0 blockTasks=380 itemSize="4.45 KiB" throttle=8192 t=2022-03-30T04:06:38+0000 lvl=eror msg="Snapshot extension registration failed" peer=51071016 err="peer connected on snap without compatible eth support"

— Reply to this email directly, view it on GitHub https://github.com/bnb-chain/bsc/issues/670#issuecomment-1082599169, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUI2RC3YHQUSZOWAUIOZJBTVCPHQJANCNFSM5KGI32YQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[Jolly23]

#856 fixed

[IronSight87]

How can I fix this problem while waiting for new release?

btw: Problem occurred after calling geth snapshot prune-block

[Jolly23]

How can I fix this problem while waiting for new release?

btw: Problem occurred after calling geth snapshot prune-block

Actually it’s not a big problem. It occurs because the removePeer was called twice. It doesn’t matter with snapSync. The problem you mentioned here is about the quality of peers you connected. They haven’t provide sync data so the sync manager removes it.