Skip to content
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

Node already synced, but after several hours its not sync again. #630

Closed
noirzz opened this issue Dec 5, 2021 · 9 comments
Closed

Node already synced, but after several hours its not sync again. #630

noirzz opened this issue Dec 5, 2021 · 9 comments
Labels
question Further information is requested

Comments

@noirzz
Copy link

noirzz commented Dec 5, 2021

Geth version: 1.1.5
OS & Version: Linux Ubuntu 20.04 LTS

Yesterday i'm trying to sync 2 bsc node with geth 1.1.5. After wait 20 hours, there 2 nodes are synced without issue. But after several hours the one node are not synced anymore and when I check the log. Its looking like this ? any solution ?
And the other one was working fine until now.

image

@noirzz noirzz changed the title Not synced, but after several hours its not sync again. Node already synced, but after several hours its not sync again. Dec 5, 2021
@a04512
Copy link

a04512 commented Dec 5, 2021

add --snapshot=false flag

@noirzz
Copy link
Author

noirzz commented Dec 5, 2021

add --snapshot=false flag

im already using snapshot false since the beginning of sync

./geth_linux --config ./config.toml --datadir ./mainnet --cache 18000 --rpc.allow-unprotected-txs --txlookuplimit 0 --http --maxpeers 100 --ws --syncmode=snap --snapshot=false --diffsync

@rmgitting
Copy link

I am having the same issue, I had a node that was always in sync, but recently I started getting such an error. What is happening to this chain?

@MohamadMousheimish
Copy link

Same issue is happening here. Any idea what's going on?

@keefel
Copy link
Contributor

keefel commented Dec 6, 2021

Please check #628 to fix

@keefel keefel added the question Further information is requested label Dec 6, 2021
@noirzz
Copy link
Author

noirzz commented Dec 6, 2021

Please check #628 to fix

on #628 say
Start your node with --snapshot=false
but im already using false since the beginning of syncing ?
so must i set it to true then false again ?

@keefel
Copy link
Contributor

keefel commented Dec 6, 2021

Please check #628 to fix

on #628 say Start your node with --snapshot=false but im already using false since the beginning of syncing ? so must i set it to true then false again ?
I think this "BAD BLOCK" error is happened when you enabled snapshot, if you have rerun it with --snapshot=false already, maybe you can update the binary and run with --snapshot=true directly.

@yutianwu
Copy link
Contributor

yutianwu commented Dec 7, 2021

If you still have issue, can you try to download the latest snapshot and restart with v1.1.7

@BinanceG11
Copy link

We have responded to the question and will proceed to close the case as we didn't get any additional question after 3days. 
Please proceed to join our Discord channel for more discussion at https://discord.com/invite/YPDsUqcwR8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

7 participants