-
Notifications
You must be signed in to change notification settings - Fork 20.4k
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
[Ropsten] Deep chain reorg breaks chain processor #17227
Comments
Ping @zsfelfoldi and perhaps @rjl493456442 (since you've been looking into bloombits lately). |
same issue on privete chain
|
This started happening when upgrading from Geth 1.8.20 to 1.8.22. I know I can fix the problem by deleting the entire chain and starting over, but resyncing this thing takes a week (and this is a pretty terrible option on a piece of infrastructure in production) and I'd like to help solve this bug if at all possible. See also #18215, #15301, #15169.
|
I am having the same issue:
|
Same thing. On Ropsten. Running v1.8.23. |
Same here, using private blockchain and geth v1.9.0-unstable-7240f4d8 |
I was getting bad block errors on Geth 1.8.21 (Ropsten), so I updated to 1.8.23.
Full re-sync? |
Same here |
same here private chain:Geth/v1.8.23-stable-c9427004/linux-amd64/go1.10.4 |
Could anyone please paste a longer dump of logs? These here contain the symptom, but not the root cause. We have a hunch it was a deep reorg that triggers it, but that should be also logged in the logs. If we could have the vicinity of the logs where this issue first starts to happen, that would be really helpful. |
I am getting this error too. |
In the end it was a corrupt chain |
same here |
INFO [05-13|02:17:19.837] Commit new mining work number=16744 sealhash=0fb7ee…723f2f uncles=0 txs this is my log I use this for start geth geth --datadir ethdata --networkid 1234 --rpc --rpcport 8545 --rpcapi "db,net, my genesis.json
|
This is supposedly fixed on master. |
Hi there,
please note that this is an issue tracker reserved for bug reports and feature requests.
For general questions please use the gitter channel or the Ethereum stack exchange at https://ethereum.stackexchange.com.
System information
Geth version: Geth/v1.8.7-stable-66432f38/linux-amd64/go1.10.1
OS & Version: CentOS 7
Expected behaviour
Synchronize the data on the test network to my network node succeessfully
Actual behaviour
has a lot of errors:
Steps to reproduce the behaviour
geth application started as command-line:
IMPORTENT INFORMATION
Geth application has no errors when started, but this a lot of error appeared when the data that has been synchronized size more than 25GB, I tried the action many times, and I have the same error.
The text was updated successfully, but these errors were encountered: