-
Notifications
You must be signed in to change notification settings - Fork 22
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
stuck at syncing #208
Comments
@kugimiya530 please join the TG channel if you still have problem with Reth BSC: https://t.me/+M9D9Eo7sMj4wNDI1 |
so fking many scam lmao
STdevK ***@***.***> 於 2024年12月6日 週五 下午1:37寫道:
… @kugimiya530 <https://github.com/kugimiya530> please join the TG channel
if you still have problem with Reth BSC: https://t.me/+M9D9Eo7sMj4wNDI1
—
Reply to this email directly, view it on GitHub
<#208 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHKNLX6ESHZU2FUY6OYT6BL2EEZYHAVCNFSM6AAAAABTAP5ZGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRSGE4DCOJRGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I had a similar issue on the more recent v1.1.0 build, running a default archive node. We were following the head when the node rolled back to block 45164942 at which point it seemingly was stuck downloading headers while trying to catch up with the head
After restarting the node seemed to get in a loop ending with the following
|
Hi @kugimiya530, Is your node working properly now? According to the logs, it seems that the peer did not respond to the data |
Hi @argakiig I checked this hash, it does not exist in the bsc history block, maybe the peer returned the block body during a fork stage This problem should be solved after restarting Software fixes still need to be resolved later. |
Describe the bug
after stage1 , it's start spaming same message and didn't syncing
Steps to reproduce
Node logs
Platform(s)
Linux (x86)
What version/commit are you on?
reth-bsc-cli Version: 1.0.7
Commit SHA: c868b94
What database version are you on?
root@BSCReth ~/Desktop/RETH # bsc-reth db version
2024-12-04T15:55:54.121228Z INFO Initialized tracing, debug log directory: /root/.cache/reth/logs/bsc
Error: Datadir does not exist: "/root/.local/share/reth/bsc"
Location:
/project/crates/cli/commands/src/db/mod.rs:76:9
Which chain / network are you on?
bsc mainnet
What type of node are you running?
Full via --full flag
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: