-
Notifications
You must be signed in to change notification settings - Fork 20.2k
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
Bloombits: "chain reorged during section processing", index upgrade stuck at 0 percent complete #15169
Comments
Any update on this? |
This is affecting two of my machines as well. Linux 14.0.04 servers, geth 1.7.3 |
For what it’s worth I backed up my keystores, completely uninstalled Ethereum/geth and reinstalled. That fixed the issue. Obvious downside is re downloading the chain. |
Issue with 1.8.2 as well. |
Hi Gorky, have you had any luck with this issue? I am getting this error on 1.8.2 stable on |
Hi, same problem with Geth/v1.8.7-stable-66432f38/linux-amd64/go1.10.1. |
Got this issue today - Geth/v1.8.11-stable-dea1ce05/linux-amd64/go1.10.3 (running on OpenSuSE Tumbleweed, connected to Ropsten) |
Running on a private network. Geth/v1.8.13 go1.10.1 geth --datadir PATH_TO/NODE init PATH_TO/genesis.json It still has to re download the whole chain, but definitely easier than uninstalling |
how to solve this problem?where is wrong? |
Probably related to #17227 |
This is supposedly fixed on master. |
System information
Geth version: 1.7.0-stable
OS & Version: Linux
Expected behaviour
The percentage complete in upgrading the chain index should be going up over the course of 12 hours, and I shouldn't be getting bloombits error messages on every block. (I presume?)
Actual behaviour
Steps to reproduce the behaviour
Upgraded geth to 1.7. Run it, with:
geth --txpool.lifetime 24h0m0s --txpool.globalqueue 1048576 --fast --cache=2048 console 2>>geth.log
Backtrace
The text was updated successfully, but these errors were encountered: