Open Mameta29 opened 1 year ago
Also I opened the same issue but this issue suit here. https://github.com/Consensys/quorum-kubernetes/issues/207
Just add the information of Geth.
Geth
i faced the same:
INFO [01-10|03:00:29.600] QBFT: handle PREPARE message address=0x27A97C9AaF04f18f3014c32e036dD0Ac76Da5f18 current.round=5 current.sequence=172,983 state=Preprepared msg.code=19 msg.source=0x98C1334496614aED49d2E81526D089f7264fED9C msg.round=5 msg.sequence=172,983 prepares.count=0 quorum=3
INFO [01-10|03:00:29.600] QBFT: handle PREPARE message address=0x27A97C9AaF04f18f3014c32e036dD0Ac76Da5f18 current.round=5 current.sequence=172,983 state=Preprepared msg.code=19 msg.source=0x27A97C9AaF04f18f3014c32e036dD0Ac76Da5f18 msg.round=5 msg.sequence=172,983 prepares.count=1 quorum=3
INFO [01-10|03:02:37.600] QBFT: handle ROUND-CHANGE message address=0x27A97C9AaF04f18f3014c32e036dD0Ac76Da5f18 current.round=6 current.sequence=172,983 state="Accept request" msg.code=21 msg.source=0x98C1334496614aED49d2E81526D089f7264fED9C msg.round=6 msg.sequence=172,983 higherRoundChanges.count=0 currentRoundChanges.count=1
INFO [01-10|03:02:37.602] QBFT: handle ROUND-CHANGE message address=0x27A97C9AaF04f18f3014c32e036dD0Ac76Da5f18 current.round=6 current.sequence=172,983 state="Accept request" msg.code=21 msg.source=0xcE412f988377e31F4d0fF12d74df73B51C42d0cA msg.round=6 msg.sequence=172,983 higherRoundChanges.count=0 currentRoundChanges.count=2
INFO [01-10|03:06:53.602] QBFT: handle ROUND-CHANGE message address=0x27A97C9AaF04f18f3014c32e036dD0Ac76Da5f18 current.round=7 current.sequence=172,983 state="Accept request" msg.code=21 msg.source=0xcE412f988377e31F4d0fF12d74df73B51C42d0cA msg.round=7 msg.sequence=172,983 higherRoundChanges.count=0 currentRoundChanges.count=1
INFO [01-10|03:06:53.603] QBFT: handle ROUND-CHANGE message address=0x27A97C9AaF04f18f3014c32e036dD0Ac76Da5f18 current.round=7 current.sequence=172,983 state="Accept request" msg.code=21 msg.source=0x98C1334496614aED49d2E81526D089f7264fED9C msg.round=7 msg.sequence=172,983 higherRoundChanges.count=0 currentRoundChanges.count=2
INFO [01-10|03:06:53.603] QBFT: received quorum of ROUND-CHANGE messages address=0x27A97C9AaF04f18f3014c32e036dD0Ac76Da5f18 current.round=7 current.sequence=172,983 state="Accept request" msg.code=21 msg.source=0x98C1334496614aED49d2E81526D089f7264fED9C msg.round=7 msg.sequence=172,983 higherRoundChanges.count=0 currentRoundChanges.count=3
i enabled emptyblockperiod, it might relate to #1630
I built a GoQuorum chain on AWS's EKS service following this tutorial: https://docs.goquorum.consensys.net/tutorials/kubernetes/deploy-charts
Overview: I was able to operate it for about a month, but suddenly blocks could no longer be produced. I was using EC2 instances for the EKS nodes, and their memory and CPU limits had been exceeded. I adjusted these and prepared sufficient EC2 instances. However, the same issue persists.
Regarding the event, a Round Change is taking place and an attempt is being made to produce blocks. There are no errors in each of the steps, but block production is not being reached. (I've posted the logs from the validators below.)
Quorum version: v22.4.0 Validators: 4 RPC: 1
Expected behaviour
The validators can generate block "51045".
Actual behaviour
They have had blocks being produced and it has suddenly stopped producing blocks.
Steps to reproduce the behaviour
I am running a validator in a Kubernetes pod, and I have restarted that pod. But still same situation here.
Backtrace
Thank you.