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
Release 1.1.0 stable cannot full sync on fast mode #329
Comments
same problem, I tried different syncmodes(snap and fast) but it didn't work;now more than 8,000 blocks behind; |
Having the same issue. Has anyone solved this problem? My hardware specs are more than enough to run a node, so it's not the problem. Changing sync modes didn't help, txlookuplimit didn't help as well |
I'm having this problem with snap sync, it's fully caught up on blocks but syncing won't end.
|
Having the same issue. knownStates and pulledStates increase but not sync finish |
Same here, synced fine before, now after the update I cannot get the node to sync. Hardware is more than enough: 12 core cpu, nvme ssd 980 pro, 128gb memory. |
@flonussi @cctanfujun @dwjpeng @Crypto2 I have a look here https://explorer.bitquery.io/bsc/calls maybe we can help does CryptoBlades (SKILL) to not do transactions for fights on blockchain :) (https://explorer.bitquery.io/bsc/smart_contract/0x39bea96e13453ed52a734b6aceed4c41f57b2271/methods) For me new issue at last 2-3 minutes of full sync: |
i ask some people, they said because of nft games,their are too many transcation,just wait about 48hours,if you are use nvme ssd |
when they can fix it? |
@lovelyrrg51 @cctanfujun they've released 1.1.1-beta which personally I am running and got synced. So give it a try :) |
Really? |
@lovelyrrg51 I have a full node started with snapshot ... which was almost synced ... I did a safe stop like crtl+c and replace the exec and I started and waited a bit ... but it got synced. |
Ah, okay, got it. |
Is 1.1.1 working for everyone? Unfortunately no luck here with it :( |
Yes |
@lovelyrrg51 do you mean your syncing has completed? |
problem with fast syncing persists in 1.1.1-beta .... |
not completed. |
@lovelyrrg51 alrights let us know how it goes. I am on 1.1.0, stable. Around 11hours into syncing, not completed yet. |
Yes, of course. |
not sure which version should be use. |
@lovelyrrg51 is this your first time setting up a node? Were you successful in previous versions before? Seems like some ppl are able to sync on 1.1.0 beta and 1.0.7 |
Not first time. |
@dracmic I thought you managed to sync up? When you said you replaced the exec file, what do you mean exactly? Do you mean you only replaced the geth_linux file from https://github.com/binance-chain/bsc/releases/download/v1.1.1-beta/geth_linux? Also how many hours did it take for your node to be fully synced? |
All of third parties including quicknode&getblock not sync complete too. |
Oooo I see. Any reason you are upgrading to 1.1.0 stable? I thought the beta version was good enough? |
@lovelyrrg51 and how long did your 1.1.0 beta version took before sync completed? |
not to 1.1.0 stable |
about 2 month |
I mean how long did your server took from scratch to achieve full sync state? 10hours? |
Ah, no |
@litebarb |
@dracmic So in summary, your node with snapshot synced, and the other node without snapshot did not sync? Can you share with us the link you used for snapshot? Is this the one? https://github.com/binance-chain/bsc-snapshots/blob/main/README.md |
@litebarb in which area you have your server maybe I can share a faster way from the server which I build ... Yes I used the the snapshot from there with syncmode="snap" ... |
@dracmic It's a custom server I have at home, I am in South East Asia |
@litebarb then that s3 link from there I think is faster to download from what I have in Europe. |
@dracmic Man I have a good connection (1 gbps) but the speed it's giving me takes me another 9hours to complete. Lol. Where can I find alternative links? |
At present, fast/snap sync is very unstable, a large number of transactions will cause more state changes, and it will become very difficult to catch up with the current state with the current implementation. We recommend that you download the snapshot we provide and run a full sync. If there is a sync issue, please report it at #338 and we will continue to update. |
CryptoBlades is intended to be entirely on chain with minimal external services. We don't really plan to do stuff like this off-chain because our users prefer us to be entirely on-chain. |
System information
Geth version:
geth version
Geth
Version: 1.1.0
Git Commit: 7822e9e
Architecture: amd64
Go Version: go1.16.3
Operating System: linux
GOPATH=
GOROOT=go
OS & Version: Linux Ubuntu 20.04
Commit hash : (if
develop
)Expected behaviour
To be fully synced and to not be behind with 100 blocks
Actual behaviour
Pivot Stale, receipts behind with ~100 blocks and the issue was also in 1.1.0-beta and actually the issue started to happen about 1 week and half ago after I saw that my node gets behind I did restart it and started this behaviour. Deleted and resynced same issue. I tried 2-3 different server providers all with NVME and a lot of RAM and different location same issue: eth.blockNumber on 0 and pivot getting stalled so I get the issue with 3 minutes back blocks (~100blocks).
Steps to reproduce the behaviour
Start a full sync ( personally I've used servers from EU countries) by using fast as syncmode
Backtrace
When submitting logs: please submit them as text and not screenshots.
The text was updated successfully, but these errors were encountered: