-
Notifications
You must be signed in to change notification settings - Fork 720
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
analysis failure: LeadDecided for noncurrent slot=SlotNo 4068 cur=SlotNo 4069
#3986
Comments
run |
I've misread the basic message, see down below. |
Whether it's true or not, can be determined from the source of truth -- the logs from the particular node -- however the error message is unhepfully not mentioning the particular node -- so we'll need to fix the error reporting here. |
Ok, so we've ran the new So it is a regression in legacy trace handling. |
Ok, giving
|
Ok, so we know it's the Next thing -- iterating over all the gigabytes of logs is slow, and we know the host, whose logs trigger this, so we now have a new subcommand --
|
What does the error message say?
What does it mean, on the most basic level? It means, that we've encountered a Hmm, so the handler for No, it's not -- there can be things that legitimately progress analysis -- and break this assumption:
Of this, the second one is not the culprit -- Hence, it must be the first one, for |
Ok, this fiasco with
|
The easy solution is to just exclude This would need some |
The text was updated successfully, but these errors were encountered: