-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
The Round Change continues indefinitely, BUT no new block is being generated. #1681
Comments
Also I opened the same issue but this issue suit here. |
Just add the information of Geth. Geth
|
i faced the same:
i enabled emptyblockperiod, it might relate to #1630 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: