-
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
BSC node can't sync the new block #162
Comments
this is bsc log |
You gotta wait, it's still syncing. You're like halfway there. |
@psdlt It's been 100 blocks away for a week |
@1b1og-com yea, sorry, i saw processed=133... and though you just started syncing, as currently there are ~200M state entries. |
@psdlt similar issue here. I've to restart the geth, mostly, the height start grew again. |
@issaxyz can you help me? what's step? why i can't sync the new bsc block and eth_blocknumber is 0 |
@issaxyz yea, after several restarts my |
@1b1og-com 2 days ago state count was ~237M:
what's your |
look
look this
|
@psdlt can you find problem ? |
i need used |
@1b1og-com your |
@psdlt I need to serve to |
I have zero affiliation with bsc, please don't @ me.
|
my wechat is wu4yyy, Let's discuss it together |
I have similar issue as well. |
I haven’t had any issues at all. You definitely need good hardware. I9+/AMD equivalent, an NVME SSD, 16GB+ of memory, and 100Mb/s or faster Internet. Another thing that could help is increasing your maximum number of peers. Also, setting Syncmode=“fast” in config.toml can help a lot |
@psdlt @stillnaughty @1b1og-com Please update your static nodes to increase connectivity
|
Having the same issue. @huangsuyu setting those static nodes didn't make a difference.
Looking at my instance stats. It doesn't seem like i'm pinning the CPU, network, or disk IO. It just seems like the application is stuck slightly behind the current state of the BSC chain. I'm running:
I'm at a loss here. What can I do to get this thing sync'd? |
You’re still importing state entries. See: ethereum/go-ethereum#16251 |
@heliosVII-tech - thanks for the link. Do you mind checking how many states there are right now? If i'm at 275M, how far do I have to go? |
Having the same problem. Tried the different StatisNodes lists given in the answers. Anyone had luck? |
@cbosss I'm at about 300M. I'd also like to know how many there are in total. I wish we could find this information somewhere. Edit: 340M, still syncing. |
Does anyone have an actual number of current total state entries?? |
catch up the latest block? |
@a04512 I don't think it has synced because the geth process shuts down after about 20s with error 1.
The bsc.log just looks like this
|
Yes there is definitely an issue right now because the sync used the work some weeks ago. |
I have the same problem, is there a potential fix ? |
I just wanted to mention I'm stuck 100 blocks behind as well on Dell R710 server v8 CPU's + SSDs. I've tried restarting geth multiple times but can't seem to get caught up. I spun up a Digital Ocean VM with SSD's and 32 CPUs and was able to get synced in about 8 hours no problem, same config files and all. I'm guessing hardware limitations requirements have gone up since the network congestion. |
@zkoolkyle it's quite surprising you get anywhere near chainhead on spinners. |
Isn't it easier to look at the blocknumber, that you can compare (e.g. on bscscan), than at states ? |
@zkoolkyle - any ideas where your droplet was located (North American, Europe, Asia...). I'm wondering if latency to other BSC nodes is an issue. |
No because you get to ~100 blocks behind current block and then are stuck there for weeks until the node picks up all states from the network. |
I ran into the same problem yesterday. Edit: The problem reappeared after some hours. |
I used data center 3 in NY. |
Which algo did you change it too out of curiosity? I assume you changed it from MQ to None |
I actually wrote a node monitoring script for this exact purpose. Just requires a free API key from BSCscan.com Link if interested: https://github.com/zkoolkyle/BSC-Node-Block-Monitor |
I switched the algorithm from |
WARN [05-04|18:19:00.005] Node data write error err="state node 91f2a5…e66b2a failed with all peers (10 tries, 10 peers)" I started a new synchronization and that is the error I got on a fresh dedicated server. |
Same for me with the node write error. |
Same issues I got.
Seems like always has the pending number, wonder why? I'm running the node with AWS c5.xlarge 4 CPU 8 GiB memory.
My questions:
|
@JohnsonCaii 8GB RAM is very little for BSC. |
I have the same problems, do you solve them all; |
I have solved these issues and have caught up with the blockchain. The things I have done:
Hope this helps! |
OK, so here is what I found: Please be advised that Binance often updates this doc: https://docs.binance.org/smart-chain/developer/fullnode.html The last week's (10.05.2021.) start command resulted in a synced state with 0 known states. Zero! But it is fully synced and is working well and fast. Here is what I think is the core problem: I was running the node in a virtual machine inside Windows, which had Ubuntu installed. I think that such a setup does not have full speed access to storage drives (namely the nvme SSD) and thus does not have sufficient IOPS to track the network. I suspect that had I installed Linux on my PC and ran it natively, I would have been able to sync, but can't confirm. Just a warning: Running i3en.2xlarge is costing be about $30 per day. Happy syncing! |
IMPORTANT NOTE: native NVMe SSD is required, AWS EBS More detail see my comment in #258 |
eth/fetcher: fix fetcher timeout (#28220)
The text was updated successfully, but these errors were encountered: