Skip to content
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

History Sync: Panic 'Election block must have validators' #1876

Closed
viquezclaudio opened this issue Sep 25, 2023 · 2 comments · Fixed by #1886
Closed

History Sync: Panic 'Election block must have validators' #1876

viquezclaudio opened this issue Sep 25, 2023 · 2 comments · Fixed by #1886

Comments

@viquezclaudio
Copy link
Member

In the private testnet (8xhistory-validators), the following panic was observed in validator-2:

thread 'tokio-runtime-worker' panicked at 'Election block must have validators': /home/nimiq/core-rs-albatross/consensus/src/sync/history/cluster.rs:223
The test conditions were as follows:

  • Validator7 & Validator8 are tainted validators: They will respond with erroneous information to the different consensus requests (history chunk, head, missing blocks, etc. )
  • All other validators are normal.
  • Validator 2 was stopped, then its state was erased and then it was restarted. During the history sync process, this validator panicked.

It is important to note that many of the validator-2 chunks that this validator requested failed to verify due to the tainted validators:
HistoryChunk failed to verify
So this validator was trying to re-request many times the history chunks and then it panicked.

@viquezclaudio
Copy link
Member Author

Attaching validator-2 logs:
privtestnet_validator2.log

@viquezclaudio
Copy link
Member Author

Tainted validators logs as a reference:
privtestnet_validator7.log
privtestnet_validator8.log

@jsdanielh jsdanielh added this to the Nimiq PoS Mainnet milestone Sep 26, 2023
viquezclaudio added a commit that referenced this issue Oct 9, 2023
viquezclaudio added a commit that referenced this issue Oct 9, 2023
@viquezclaudio viquezclaudio mentioned this issue Oct 9, 2023
3 tasks
viquezclaudio added a commit that referenced this issue Oct 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants