-
Notifications
You must be signed in to change notification settings - Fork 567
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
privval: duplicate SignerListener: Listening for new connection module=privval
during chain upgrades
#3828
Comments
Several validators experienced this problem during the recent If you're a validator who experienced this problem, 👍 this message. We also experienced it on the most recent Neutron upgrade, and I believe the one before that. If you've experienced it on other chain upgrades, please leave a comment and perhaps we can help narrow down the CometBFT version where this bug was introduced. |
Can confirm I had the same issue with recent Neutron upgrades |
Are you upgrading from which version to which version? |
Here's more logs of the full node startup:
This part in particular seems a bit weird:
Right after it successfully accepts a privval connection, it seems to start listening for a new one. |
@cason this was upgrading to v0.38.9. I'm not sure what the previous release of Edit: I think the previous CometBFT version was v0.37.6 |
Resolve #3828 On cometbft startup, duplicate privval request can enter the channel between the time listen begins and a send is attempted. The duplicate listen request will timeout since there is not another signer connecting, filling logs with errors. A duplicate listen request is undesired. --- #### PR checklist - [x] Tests written/updated - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments --------- Co-authored-by: Anton Kaliaev <[email protected]> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by: Daniel <[email protected]>
Resolve #3828 On cometbft startup, duplicate privval request can enter the channel between the time listen begins and a send is attempted. The duplicate listen request will timeout since there is not another signer connecting, filling logs with errors. A duplicate listen request is undesired. --- #### PR checklist - [x] Tests written/updated - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments --------- Co-authored-by: Anton Kaliaev <[email protected]> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by: Daniel <[email protected]> (cherry picked from commit 5562f11)
Resolve #3828 On cometbft startup, duplicate privval request can enter the channel between the time listen begins and a send is attempted. The duplicate listen request will timeout since there is not another signer connecting, filling logs with errors. A duplicate listen request is undesired. --- #### PR checklist - [x] Tests written/updated - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments --------- Co-authored-by: Anton Kaliaev <[email protected]> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by: Daniel <[email protected]> (cherry picked from commit 5562f11) # Conflicts: # privval/signer_listener_endpoint.go
Resolve #3828 On cometbft startup, duplicate privval request can enter the channel between the time listen begins and a send is attempted. The duplicate listen request will timeout since there is not another signer connecting, filling logs with errors. A duplicate listen request is undesired. --- #### PR checklist - [x] Tests written/updated - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments --------- Co-authored-by: Anton Kaliaev <[email protected]> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by: Daniel <[email protected]> (cherry picked from commit 5562f11) # Conflicts: # .changelog/v0.38.3/bug-fixes/3828-privval-drop-duplicate-listen.md
…port #3830) (#3895) Resolve #3828 On cometbft startup, duplicate privval request can enter the channel between the time listen begins and a send is attempted. The duplicate listen request will timeout since there is not another signer connecting, filling logs with errors. A duplicate listen request is undesired. --- #### PR checklist - [x] Tests written/updated - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments <hr>This is an automatic backport of pull request #3830 done by [Mergify](https://mergify.com). Co-authored-by: Chill Validation <[email protected]>
…port #3830) (#3896) Resolve #3828 On cometbft startup, duplicate privval request can enter the channel between the time listen begins and a send is attempted. The duplicate listen request will timeout since there is not another signer connecting, filling logs with errors. A duplicate listen request is undesired. --- #### PR checklist - [x] Tests written/updated - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments <hr>This is an automatic backport of pull request #3830 done by [Mergify](https://mergify.com). --------- Co-authored-by: Chill Validation <[email protected]> Co-authored-by: Anton Kaliaev <[email protected]>
…port #3830) (#3896) Resolve #3828 On cometbft startup, duplicate privval request can enter the channel between the time listen begins and a send is attempted. The duplicate listen request will timeout since there is not another signer connecting, filling logs with errors. A duplicate listen request is undesired. --- #### PR checklist - [x] Tests written/updated - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments <hr>This is an automatic backport of pull request #3830 done by [Mergify](https://mergify.com). --------- Co-authored-by: Chill Validation <[email protected]> Co-authored-by: Anton Kaliaev <[email protected]> (cherry picked from commit 221c744)
…port #3830) (backport #3896) (#3900) Resolve #3828 On cometbft startup, duplicate privval request can enter the channel between the time listen begins and a send is attempted. The duplicate listen request will timeout since there is not another signer connecting, filling logs with errors. A duplicate listen request is undesired. --- #### PR checklist - [x] Tests written/updated - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments <hr>This is an automatic backport of pull request #3830 done by [Mergify](https://mergify.com).<hr>This is an automatic backport of pull request #3896 done by [Mergify](https://mergify.com). Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
…port #3830) (#3897) Resolve #3828 On cometbft startup, duplicate privval request can enter the channel between the time listen begins and a send is attempted. The duplicate listen request will timeout since there is not another signer connecting, filling logs with errors. A duplicate listen request is undesired. --- #### PR checklist - [x] Tests written/updated - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments <hr>This is an automatic backport of pull request #3830 done by [Mergify](https://mergify.com). Co-authored-by: Chill Validation <[email protected]> Co-authored-by: Anton Kaliaev <[email protected]>
Bug Report
Setup
Config
What happened?
During a chain upgrade, CometBFT seemingly attempts to accept two
privval
connections. TMKMS only opens one such connection, which otherwise works/remains stable. But in the logs (see below), the node continues to print the following in a loop, which is confusing to users during a chain upgrade and spammy in logs during a time when people are trying to keep an eye on them to figure out what happened.What did you expect to happen?
These lines do not appear in the logs, though they seem to be a symptom of a deeper problem.
How to reproduce it
This is the tough part: we only witness this during a chain upgrade. It has impacted several recent chain upgrades however, including today's gaia v19 upgrade as well as recent Neutron upgrades.
It seems to be happening with every recent chain upgrade, however, when TMKMS is being used as a remote signer.
The problem persists after the chain has started, but can be fixed after a chain upgrade has completed by restarting the node.
Logs
The TMKMS side shows a stable connection without problems:
Anything else we need to know
This doesn't actually break anything, though it is very confusing during chain upgrades, and introduces a red herring when people are otherwise trying to debug TMKMS issues (e.g. people interpreted this error as potentially being a problem with enabling extension vote signing, even though everything was working)
The text was updated successfully, but these errors were encountered: