-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ethereum peer removal failed peer=-------- err="peer not registered" #670
Comments
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. |
but the syncing has stopped from last few hours... |
Probably not related to that error. |
Can you please share the logs and please check its simillar to your issue it might be solve your problem ethereum/go-ethereum#22077 |
I'm having the same issue where it says "Ethereum peer removal failed" and the sync just stops dead. |
@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. |
Linked to #220 |
@forcodedancing no node is not recovered, still same issue |
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 :/ |
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 Android<https://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 @forcodedancing<https://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 GitHub<#670 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATHSSIW77UNJVM5T7LNTMKTUVVXO5ANCNFSM5KGI32YQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://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: ***@***.***>
|
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. |
@forcodedancing Any update on this? My node keeps dropping blocks because of the above issue |
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" |
I am having this exact same issue constantly.Now 100,000 blocks behind the main network because of this error
|
same issue
|
เมื่อ 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
<#670 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUI2RC3YHQUSZOWAUIOZJBTVCPHQJANCNFSM5KGI32YQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
#856 fixed |
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. |
bsc node has downloaded snapshot and now syncing from chain after a while suddenly started showing above error, can some one help pls
The text was updated successfully, but these errors were encountered: