-
Notifications
You must be signed in to change notification settings - Fork 211
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
Invalid bloom error thus shutting down chain bootstrap #1114
Comments
validators that run with the old code (<v0.6.0) after Durango has created a faulty state. Did you copy from a validator DB to new nodes? If so they also have this faulty state. We're working on a way to mitigate missed upgrades. |
we have 7 validators, 4 of them were operating normally but the other 3 fall in to this state. I copied db from one of the four validators to the others to mitigate the issue. |
Hello there! |
Hello I have upgraded to avalanchego-v1.11.4 and subnet-evm_0.6.3 but it couldn't detect
EDIT |
Short story: We recently missed the the major Warp messaging (Fuji) update, the subnet stopped 3 days, after we synchronized all of the archieve nodes and rpc's with copying the db. However now a new rpc nodes which tries to enter the subnet receives Fatal error and shuts down the bootstrapping process.
Describe the bug
Somehow subnet produces a dirty block and inserts through all of the validators, then newly entered node fails to bootstrap the subnet chain.
I am sharing the both of the archive validator node and a recent node ( which is just indexing node ) logs. After creating a certain block ( 2PGQzuTjzBEcVqTnNmVwhAsk4PsXV88M7DT7wRtgmC973J4TVf ) the validator kills the subnet subprocess.
The last line of the recently joined rpc node gives the following error and shuts down
Logs
1- The subnet archive validator node logs (truncated till that faulty blockID):
2- The recent rpc node enters the network. The last line gives the FATAL error.
Operating System
Debian 11 x64
Any help or clarification will be appreciated
The text was updated successfully, but these errors were encountered: