-
Notifications
You must be signed in to change notification settings - Fork 536
failed to consensus: unable to read new message from the message queue #579
Comments
Hey @xingxinglian, Which commit hash are you running on from the |
@zivkovicmilos I use the commit 8b85d68 , May 20 |
Got it, are you able to reproduce this problem with the latest commit? We've added mechanisms in place that will prevent this kind of situation from occurring: |
@zivkovicmilos got it. I will pull the newest code to try it. And I want to know to what's mechanisms to prevent; I already read the new code , but can't get how to prevent. |
Hey @xingxinglian, There are several things that prevent it, actually. One of the most obvious ones is that we've added improved block verification that will not cause your network to get confused when irregular blocks are proposed. This has been resolved and is live on the develop branch. The other major thing that caused this sort of behavior is bad unlocking mechanisms that are in place in the current IBFT implementation. We've since resolved this in an open PR. Let me know if you still experience these problems after you've pulled the latest Also, please make sure your nodes are actually online and connected. |
@zivkovicmilos thanks, I already pull code and run online. If still occur the problem , I'll tell you. |
@zivkovicmilos Facing same issue I tried with latest release (v0.4.1) which has commit 06dc155 and even tried to setup freshly. Here are my working logs for TESTING:
|
Hi @spunkyshooter , Are you running only 2 nodes out of 4 ? Thanks |
Yes, I ran only 2 out of 4 nodes and noticed the issue.
|
@spunkyshooter Great 🥇 There needs to be at least 4 validators active at minimum in order for the blockchain network to run properly. I'll close this issue for now. Feel free to open a new issue if you face any more problems. |
[Subject of the issue]
Description
I deploy polygon-edge for 3 validator nodes, use pos consensus.
after run more than 20 hours, the system can't generate blocks. after analysis the log, I found the three node all have something wrong with the "unable to read new message from the message queue: timeout expired=5m0s". then I restart the proposal validator node, the system run ok.
Your environment
ubuntu 22.04
polygon edge develop branch
Steps to reproduce
run 20 hours, all nodes in the same machine
Expected behaviour
Is there any optimize for the system self-cure replace restart nodes ?
Actual behaviour
the system can't generate blocks
Logs
Proposed solution
maybe in the case , the validators should step in sync state
The text was updated successfully, but these errors were encountered: