-
Notifications
You must be signed in to change notification settings - Fork 152
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
clique perpetual resync from ~block3000 #75
Comments
I ran the following to stress test geth with some repeated uncatchable kills
Caught the following.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Visible on Kotti.
For some geth clients on Kotti (a clique consensus network), they can be seen to sync with the network and then eventually "rewind"/"fall back"/whatever to about block 3000, and then do a whole lot of
heavy sidechain
imports.More information and investigation to follow.
An example log file which has been filtered to try to show most relevant lines: https://gist.github.com/4fc03ad11e22ce8c1de032b4add94b96
cat core-geth.kotti.fullsync.service.logs | grep -v -E '(admin_peers|stats|peer|Suppressed|Deref|handshake|Served|Writing prev|Inserted known|QoS|Bad packet|Revalidated node|Removed dead node|Bad discv4)' > core-geth.kotti.resync.log.filtered
)The text was updated successfully, but these errors were encountered: