Skip to content
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

ERR failed signing vote err="error signing vote: round regression at height 32744. Got 3, last round 24 #9394

Closed
4 tasks
seedlings-calm opened this issue May 26, 2021 · 4 comments
Assignees
Labels
S:needs more info This bug can't be addressed until more information is provided by the reporter.

Comments

@seedlings-calm
Copy link

The cause of the problem is not yet known. I don’t know whether it’s learning to understand the cosmos sdk. It’s simple or unknown. I hope your team can help solve this problem. Thank you very much

Summary of Bug

ERR prevote step: ProposalBlock is invalid err="wrong Block.Header.AppHash. Expected 8A90F675BFE08468C597E4F7E17128A5EC6D16D1F841AA5A98EDCD4C1B1AA506, got BA85B26965328240B16141DB023200902789E656C23D4A8049504832E6758B73" height=32744 module=consensus round=3
11:42AM ERR failed signing vote err="error signing vote: round regression at height 32744. Got 3, last round 24" height=32744 module=consensus round=3 v

Version

cosmos-sdk v0.42.3
golang v1.16
tendermint v0.34.8

Steps to Reproduce

Cause: The three validator nodes are working normally, the wasmd v0.15.1 was introduced from the code base, swagger control was written, the binary file was regenerated, and the validator node was restarted, resulting in no new blocks.

node1:
nohup onpchaind start --unsafe-skip-upgrades 32744 --log_format json --log_level debug --home node1 >> node1.log 2>&1
node1.log
node2:
nohup onpchaind start --unsafe-skip-upgrades 32744 --log_format json --log_level debug --home node2 >> node2.log 2>&1
node2.log
node3:
nohup onpchaind start --unsafe-skip-upgrades 32744 --log_format json --log_level debug --home node3>> node3.log 2>&1
node3.log


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@tac0turtle
Copy link
Member

Hey, your application has some non determinism. The apphash divergence is caused by application state diverging between nodes.

@seedlings-calm
Copy link
Author

The contents of the priv_validator_state.json files of the three nodes are not synchronized. Is this caused? Can you tell me where to start to deal with this problem?

@tac0turtle
Copy link
Member

The contents of the priv_validator_state.json files of the three nodes are not synchronized. Is this caused? Can you tell me where to start to deal with this problem?

Are you running three nodes with the same private key?

This usually stems from the state machine not tendermint. What app are you running?

@aaronc aaronc added the S:needs more info This bug can't be addressed until more information is provided by the reporter. label May 28, 2021
@tac0turtle
Copy link
Member

Hey, I'm going to close this issue for now. Please ping me in the cosmos discord with any further questions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S:needs more info This bug can't be addressed until more information is provided by the reporter.
Projects
None yet
Development

No branches or pull requests

3 participants