-
Notifications
You must be signed in to change notification settings - Fork 721
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
[v6.0.2] Error during startup #1280
Comments
Hi @muratso the official release version for mainnet is still Vega v6.0.0 |
Since the v6.0.2 had been officially released and tagged as "latest", I assumed it was safe to use it. In this case, I'm going to restore from a backup and roll back my node to v6.0.0 :). Thanks for the info. |
@muratso Just going to keep this open to continue investigating |
hi @muratso you're correct it is assumed that v6.0.2 is correct and can be run. |
also happy to connect in a more synchronous channel than github if you have an email, telegram or discord handle |
🤔 Let me give it a try in one thing. If it's safe to use it, let's assume something got corrupted during the node shutdown when I was upgrading it. I'll try to restore the disk from a snapshot and retry the upgrade. |
@muratso hey, thanks for pointing this out. Could you post your pruning setting for your node? |
thank you @muratso ! |
Hi @muratso we've also now detected nondeterminism. Please use v6.0.0 until we find the source of the breaking change. |
@marbar3778 just answering your question while I restore the disk. We haven't tuned the prune options, so I believe we're using the default for pretty much all the options related to pruning.
|
@okwme |
This is the consensus failure I encountered:
|
tested locally is fine: but live hub is incompatible with v6.0.2, @glnro |
6.0.2 is redundant now because of the consensus bug and should not be used, use 6.0.3. |
Summary of Bug
After upgrading my node I started seeing the error below. I haven't done anything special to get this error.
Version
v6.0.2
Steps to Reproduce
Simply upgraded the node from 6.0.0 to 6.0.2
For Admin Use
The text was updated successfully, but these errors were encountered: