-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Gaiad cannot reconnect KMS unless restart gaiad #3190
Comments
This seems like a dupe of: |
@tarcieri is that included in a release yet? |
To my knowledge this specific bug is addressed in 0.29 (see tendermint/tendermint#2876) however there is a similar-but-distinct issue tendermint/tendermint#2923 which is as-yet-unresolved but I believe does not result in this specific failure mode. |
I can also reproduce a situation where even if the connection with the KMS is still present, This directly affects Ledger's initialization. Repro steps:
After that, it will never request signatures from the KMS again.
|
Linking tendermint/tmkms#172 as a related issue |
👍 |
ref: tendermint/tendermint#2923 (comment) for the 2nd case This does not solve the 1st issue though. |
@yulidai Were you running a single node? |
@jleni We've fixed this upstream, right? In any case, this is a Tendermint issue, not an SDK issue. |
It's ok, thanks |
Summary of Bug
In order to use
tendermint/kms
with gaiad, i'm changing thepriv_validator_laddr
, then they connect success and it's good to work together.But problem occured after restarting kms, gaiad will keep printing
Ping module=privval err="remote signer timed out"
. They will never be able to reconnect unless i restart gaiadSteps to Reproduce
Start kms.
Start gaiad with kms's pubkey.
Then restart kms
Edit:
gaiad version: 0.28.0-0-g68019be
tmkms's version: 0.23
Edit2:
Same problem with version: 0.29.0-0-g2b3842c
For Admin Use
The text was updated successfully, but these errors were encountered: