-
Notifications
You must be signed in to change notification settings - Fork 20.3k
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
Not able to full sync Ropsten network past block 6491959 #22497
Comments
|
@holiman Hello! Startup command: About my machine: |
Ok, thanks. Well, that looks ok, so could you provide a bit more of that stacktrace, so we can see where it comes from? Without knowing any more, one possible source could be if attackers on the internet overloading it with RPC queries. |
Hello @holiman ! I've tried re-syncing everything from scratch, but the exactly same scenario happened, it stucks at block 6491959. This is the full log, it starts just some minutes before the crash happens:
|
Just a quick update, using |
Story time Before it was destructed, a total of 307,430 txs had made use of it. That block is 1060 blocks earlier than the block we got stuck at ( Previously, without snapshot, a large contract going away was not a problem -- we just set the stateroot to I suspect that the same scenario may cause problems for other clients, e.g. turbo-geth, which have some concept of flat-database and/or reverse state diffs, hence the write-up. So cc @AlexeyAkhunov @draganrakita @RatanRSur @tkstanczak -- this ropsten transaction is a pretty good test for how the client handles that. |
cc @matkt |
System information
Geth version: Gemini Sigma (v1.10.1)
OS & Version: Debian GNU/Linux 9.6 (stretch)
Commit hash : c2d2f4e
Actual behaviour
I'm syncing Ropsten network from scratch in full mode. I'm not able to get past block 6491959 (found using web3.eth.syncing). Geth stucks there, sometimes it crashes due to out of memory error (please see the backtrace below) sometimes it just restarts syncing from around block 6488206. And then it gets stuck again at block 6491959, restarting the cycle.
Steps to reproduce the behaviour
I've updated Geth to the latest version and then restarted the node. I've also updated Go to version go1.16 linux/amd64.
Backtrace
The text was updated successfully, but these errors were encountered: