-
Notifications
You must be signed in to change notification settings - Fork 277
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
[BUG] "This peer is faulty." "Restarting consensus(internal bug). Report to developers" No new blocks get created. #5230
Comments
Here are some new logs after restarting a node. It tries to generate consensus but eventually fails: Log contents
|
I'm still experiencing this issue:
|
This error seems to be different from the one originally reported. Are you still experiencing both errors, or has one been partially resolved? Just to let you know, we recently released version 2.0.0-rc.1, and this issue may have already been resolved in the latest version. The JavaScript SDK is also being updated, so we recommend upgrading to the latest release. cc: @0x009922 |
I experienced both, but the latter is the one recurring. I think I figured out the first issue |
@0x009922 Do you know If I can use js SDK v7.1.0 with iroha 2.0.0-rc.1 ? I'm on 2.0.0-pre-rc.20. |
@matisalimbene you certainly cannot use I am working hard on the support of |
OS and Environment
hyperledger/iroha2:stable-2.0.0-pre-rc.20
GIT commit hash
5d44d59
Minimum working example / Steps to reproduce
I'm simply running an Iroha2 network and then adding new nodes. Everything seems to work, then it doesn't. Once I start getting the "Faulty peer" and "Restaring consensus (internal bug)" error, the consensus fails and no new blocks get created.
Actual result
2m2024-10-23T17:15:03.735738Z0m 31mERROR0m 2miroha_core::sumeragi0m2m:0m This peer is faulty. Incoming control messages have to be dropped due to low processing speed. 3merror0m2m=0m"Full(..)"
2m2024-10-23T17:15:08.559967Z0m 31mERROR0m 1mconsensus0m2m:0m 2miroha_core::sumeragi::main_loop0m2m:0m Rotating the entire topology. 3maddr0m2m=0miroha3:1340
2m2024-10-23T17:15:08.560120Z0m 31mERROR0m 1mconsensus0m2m:0m 2miroha_core::sumeragi::network_topology0m2m:0m Restarting consensus(internal bug). Report to developers
Expected result
2024-10-22T11:35:33.453135Z INFO consensus: iroha_core::sumeragi::main_loop: Committing block addr=iroha0:1337 role=ProxyTail block_height=5 block_hash=6e86dd99781773aa26fc893b369061e95ef3e9ab361e2e412c515a662e88b257
Logs
Log contents
Who can help to reproduce?
No response
Notes
Initially I start the network with a docker compose file as follows. After that is up and running, new peers start to join, until it the error appears:
The text was updated successfully, but these errors were encountered: