Rejected by VP after trying to unjail-validator caused by change-consensus-key command
#2642
Comments
spidey-169
changed the title
change-consensus-keycommandchange-consensus-key command
spidey-169
changed the title
change-consensus-key commandchange-consensus-key command
|
Having the same with the following output: |
|
I haven't used the change-consensus-key command, instead while upgrading I replaced with a new set of keys during validator initiation. Waited for 2 epoch, validator was added in epoch 6. But in epoch 7 the validator was jailed. I have checked for slashed didn't find any, and liveness of the node is also fine. |
|
@brentstone Apologies for tagging you. Any luck or ideas here to fix this issue? Changing consensus keys is a pretty standard operation and this bug is currently causing our validator to be stuck. Thanks |
|
Thanks for tagging! We're still investigating. The restart patch v0.31.5 only fixed the source of the consensus failure and chain halt for now. Will update when we've made some progress here. |
|
Was able to unjail when fully synced Seems some ppl still have the problem |
|
@Liver-23 oh wow, ok, thanks for reporting this to us, definitely appreciated. I'm going to link this issue in a more global one. |
Same here @brentstone , was able to unjail miraculaously after fully syncing, though I think there are numerous others still stuck. Thanks for linking this issue to a global issue 🙂 |
|
@brentstone Hello, today since epoch 10 my validator has been jailed. Unjail command logPublic key: As I remember, I did not use an |
Hello, my validator is in jail and I can't get it out. |
|
I have the same issue, I am not able to unjail my validator. However, I was not changing consensus key. Seems like I was jailed some time after the today's restart (https://discord.com/channels/833618405537218590/1196488611613376574/1209245372745130044). Output |
|
have the same issue! i never changed my consensus key. |
|
Same as the others. Never changed consensus key. Can't unjail. |
|
Same I can't unjail |
|
I just checked all the addresses of the VPs who rejected my unjail transactions. They all are validators who are not in the active set anymore. After rejected check the address with: namadac validator-state --validator "ADDRESS" |
|
Same problem. Cant unjail after change consensus key. My validator is: tnam1q96tsxckvm4n937efh7t78w4j40m5783wsqcz3ye. |
|
all the VPs mentioned above are either jailed or below-capacity set |
|
How do I choose a validator from the active set to get out of jail? |
|
Same I can't unjail namadac unjail-validator --validator 'tnam1qxc0ypga9n4mcdscqqdrt38ph573tjh3uvu6q4aj' |
On my side, I am being rejected by validators who are |
|
Same problem here, jailed since epoch 12, and we can't unjail: Looking-up public key of tnam1q9kdhreynpfg5c2wvnwvherfl3jmuz6rlq09yqcp from the ledger...
Transaction added to mempool.
Wrapper transaction hash: 1B8756A76C9F1BDAAB57EC5742F7F3373F0B28E450A17588A984C85D833930D3
Inner transaction hash: BC3C46EE6CEB36F9D078820C7C431970AC56F25784ADD887DEFBBB13311BF45B
Wrapper transaction accepted at height 70586. Used 23 gas.
Waiting for inner transaction result...
Transaction was rejected by VPs: [
"tnam1q9re7cpzcew5xjkea24xcuemw7jyax48tqfdqgem"
].
Changed keys: [
"#tnam1qgqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqc8j2fp/validator/#tnam1q9kdhreynpfg5c2wvnwvherfl3jmuz6rlq09yqcp/state/last_update",
"#tnam1qgqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqc8j2fp/validator/#tnam1q9kdhreynpfg5c2wvnwvherfl3jmuz6rlq09yqcp/state/lazy_map/data/000000000000I",
"#tnam1qgqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqc8j2fp/validator/#tnam1q9kdhreynpfg5c2wvnwvherfl3jmuz6rlq09yqcp/state/lazy_map/data/000000000000O",
"#tnam1qgqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqc8j2fp/validator/#tnam1q9kdhreynpfg5c2wvnwvherfl3jmuz6rlq09yqcp/state/lazy_map/data/000000000000Q",
"#tnam1qgqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqc8j2fp/validator/#tnam1q9kdhreynpfg5c2wvnwvherfl3jmuz6rlq09yqcp/state/lazy_map/data/0000000000010",
"#tnam1qgqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqc8j2fp/validator/#tnam1q9kdhreynpfg5c2wvnwvherfl3jmuz6rlq09yqcp/state/lazy_map/data/0000000000018",
"#tnam1qgqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqc8j2fp/validator/#tnam1q9kdhreynpfg5c2wvnwvherfl3jmuz6rlq09yqcp/state/oldest_epoch",
"#tnam1qgqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqc8j2fp/validator/#tnam1q9re7cpzcew5xjkea24xcuemw7jyax48tqfdqgem/state/last_update",
"#tnam1qgqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqc8j2fp/validator/#tnam1q9re7cpzcew5xjkea24xcuemw7jyax48tqfdqgem/state/lazy_map/data/0000000000018",
"#tnam1qgqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqc8j2fp/validator_set_positions/lazy_map/data/0000000000018/data/#tnam1q9kdhreynpfg5c2wvnwvherfl3jmuz6rlq09yqcp",
"#tnam1qgqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqc8j2fp/validator_set_positions/lazy_map/data/0000000000018/data/#tnam1q9re7cpzcew5xjkea24xcuemw7jyax48tqfdqgem",
"#tnam1qgqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqc8j2fp/validator_sets/below_capacity/lazy_map/data/0000000000018/data/FVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVBNG1FVG/data/00000000000KU",
"#tnam1qgqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqc8j2fp/validator_sets/consensus/lazy_map/data/0000000000018/data/000000000000000000000000000000000000000000000K8FUG00/data/0000000000010",
"#tnam1qgqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqc8j2fp/validator_sets/consensus/lazy_map/data/0000000000018/data/000000000000000000000000000000000000000000164982TV00/data/0000000000000"
] |
|
Same problem |
|
JAIL since epoch 18
|
|
Same problem. |
|
Same problem. |
|
the same( cant unjail |
|
Got the same issue. The validator rejected is in the below-capacity set at epoch 19. Rejected by another validator at epoch 20 which is in the consensus set. I would also be rejected by my own validator which is jailed. |
|
Same issue, posting here to be notified on updates |
|
Additions to #2617 have been made that we believe solve this issue. Stay tuned for when these changes will be included in a release. |
Great work Brent! |
|
After unjail my node is in consensus , but does not vote for any blocks namada client validator-state --validator tnam1qy24smlm8tdg8vawx8xh30fxa8kcwnudkvufz9zn --node https://rpc.namadascan.io/ Validator Address: F15F1EA313631C31B67C61B3EF52FE23D1B31E29 - Signed: 0, Missed: 50, Ratio: 0% |
|
@Igor-Tselkovskiy did you ever restart your node after changing consensus key? |
I didn't change the consensus key. |
|
@Igor-Tselkovskiy ok let's continue the discussion on Discord rather than on this GH issue - you can find me as |
|
Closing, let's continue discussion on #2663 if needed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Issue description
change-consensus-keycommand to create a new key and switch to itResult: the message about key change appears with a notice that you need to change priv_validator_key as well 2 blocks before the new epoch. It was working fine after, hence didn't think too much to it
I tried unjailng with the existing key a few times, between restarting node and unjailing. But it failed with a VPs rejection. I have seen this reported by almost everyone who gets jailed and unjails. So kept trying this first to fix it
Next, I decided to look into consensus-key-change. I was not sure how to change keys at all, and currently there was no internal functionality to do but there was ongoing discussion here #2516 on a method
change-consensus-keyto create a validator.json key corresponding to new consensus key. So I decided to use it.This
Consensus key: tpknam1qq4d7g6e0p50wkatsr2tmr74ctucryd93dtvflj50xppr4ztz8m2688y7nxis my new consensus key, hence I confirm that new consensus key should be singing blocks, so ideally this should allow me to unjail as I have the correct key. But it doesn't work.And got the same error. Have tried this a couple of times but txn just doesn't go through.
In summary, validator got jailed due to
consensus-key-chageand have since not been able to unjail it Either using old or new consensus key. THere are no other keys on this wallet.toml file. Just my validator established account and my Pilot Implicit wallet.The text was updated successfully, but these errors were encountered: