-
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
Syncing 3 days behind every time #439
Comments
Hello, what about your config.toml and start geth command arguments? if target make full sync then GP3 more than needed, basic GP2 enough for me and costs 2x less. |
Could you share your config.toml file and the command pls? I'm having the same issue. Synced few days ago but now always 100ish blocks behind |
Here is my config.toml file @0fuz :
And the command I am using to run the node:
And this is the current log:
|
did you try snap syncmode when starting geth with "--syncmode snap"? |
No I haven't tried with |
Using snap syncmode was the only way I was able to successfully sync my node. |
finally synced after so many days... |
What syncmode did you use to sync? |
default |
@urkishan config.toml part:
For 32gb RAM i'm using 1d ago this setup gave me average 2-3 block sync in a second |
So @0fuz should I increase my |
yes, hope it can help, geth depends of RAM a lot |
I don't understand why they are not solving this issue, As this is not my first issue in here I've raised related to the syncing problem. They should really provide a full documentation how to sync or let us know that they are having some problem. Here is my other issue I've raised for them but I didn't get any help from this team #258 |
And here we have something else I don't know if it is a normal behaviour or something else:
The |
when your currentBlock so far from highestBlock, highestBlock might not be real latest network known. |
I had 100 blocks behind too, and solved it by making full sync from bsc-snapshots |
Looks like you're syncing 1 block a second? You may still catch up but it will take ages... |
BTW, I used 1000 peers in my conf file |
My node is still 3 days behind. I don't know what is going on. Can somebody let me know what should I do? |
@DryDragon10 your node is synced? |
Yes mine has been synced fine for a week |
can you post your status here? |
Guys, this is still unclear. What should I do to sync a full-node? I've been trying for a week now... |
@DryDragon10 @risingsun007 |
I saw similar change of 'currentBlock' after I made aws.volume.snapshot and unzipped it, I solved it by downloading latest snapshot( |
|
I am still not able to solve this issue, it seems I've to reinstall the BSC chain. |
This is just way too slow. It seems that your vps doesn't meet the requirements of a full node |
Hi DryDragon10, did you have your node successfully synced from scratch or a snapshot copy from https://github.com/binance-chain/bsc-snapshots? |
I've started 3 node for syncing from more than 1 week but it still nothing. I think it's time to move to other blockchain because they aren't supporting and telling us anything that what is going on. |
@urkishan please check this gist https://gist.github.com/0fuz/43960fd99507c587b45c77daba91e90c |
tl:dr; but if you are experiencing huge block loss after restarting geth, you should maybe start it as a daemon and configure the timeout to around 5 minutes - this way it has time to persist the data from memory to disk. |
I could barely sync my server in about 12h after 2 weeks of trying different stuff. I previously had a regular SATA SSD(Intel DC enterprise part), then upgraded to a Samsung NVME but using a ZFS format == fail. Then I formatted it to XFS(a lot of people suggested this for geth/leveldb performance) and like magic it worked in under 12h. The point is IO performance is critical Now the only issue is that sometimes it laggs 1-2 blocks, but I guess the network is really congested(a lot of official nodes are out of sync by upto 40 blocks sometimes), see https://bscscan.com/chart/tx I wrote a quick script to check some public nodes(it just queries current block): [latency test] 357ms for https://bsc-dataseed1.ninicoin.io/ is 6 blocks behind!!! |
would you mind sharing your query script? |
@icex Not in my case. Ubuntu 20.04 , 8-core Ryzen, 32GB RAM, NVME 180k IOPS. Ubuntu is installed on ext4 partition, bsc data on partition with xfs file system. Syncing 3 days , still 30k blocks behind latest. Can you please share your config.toml file and start command? |
I'm running a Supermicro server with Xeon(R) Silver 4210 CPU @ 2.20GHz (10c/20t cpu), 64GB ram, Samsung 970 EVO Plus 2TB NVME. But it is also running stuff as well. config.toml
start command ./geth_linux --snapshot=false --syncmode fast --diffsync --config ./config.toml --datadir ./mainnet --cache 8000 --rpc.allow-unprotected-txs --txlookuplimit 0 |
We have responded to the question and will proceed to close the case as we didn't get any additional question after 3days. |
@urkishan Could you resolve this issue finally? |
System information
AWS Instance
Disk Configurations :
Geth version:
The blockchain was synced before but when I restarted It is now 3 days behind. I don't know what is wrong with the BSC network. My entire system is suffering because of this. Kindly anyone help me to resolve this.
I've done everything as you can see the configurations. It seems I am installing a project of NASA.
Here is the out for
eth.syncing
The text was updated successfully, but these errors were encountered: