[BUG] "This peer is faulty." "Restarting consensus(internal bug). Report to developers" No new blocks get created. #5230
Labels
Bug
Something isn't working
Comments
|
Here are some new logs after restarting a node. It tries to generate consensus but eventually fails: Log contents |
|
See the topology bellow, these are the 7 peers, all "alpha" nodes are running. Others do not. I notice there one peer repeated, same ip/port (100.112.24.100) but different public key. I would've thought this could not be possible, I mean registering the same IP/Port configuration more than once, but looks like as long the public key is different it would register the node again. {
PeerId{
address: SocketAddrHost{
host: "100.112.24.100",
port: 1347
},
public_key: {
digest: ed25519,
payload: ed012016A448A28AB84A44E7945822E5B425969E2D7DADEAFF314CCF3EE44E9E7BF2F7
}
}: false,
PeerId{
address: SocketAddrHost{
host: "alpha.openspacenetwork.org",
port: 1339
},
public_key: {
digest: ed25519,
payload: ed01204D743DBC95C0E91A5D50E6B56C76577E7AF456664E0F2BFB931F7C2748300205
}
}: false,
PeerId{
address: SocketAddrHost{
host: "100.73.34.108",
port: 1347
},
public_key: {
digest: ed25519,
payload: ed01200737FB30F5DCC781C80EE344072CD3BA4246D6D801791E31C1C163109E049CF8
}
}: false,
PeerId{
address: SocketAddrHost{
host: "alpha.openspacenetwork.org",
port: 1340
},
public_key: {
digest: ed25519,
payload: ed012017D319438B343995848F112BEB38695D3AA696C71257D52B12D630FD0099B792
}
}: false,
PeerId{
address: SocketAddrHost{
host: "alpha.openspacenetwork.org",
port: 1337
},
public_key: {
digest: ed25519,
payload: ed0120F4496DE85F18A88899FD1CF49DA19AFE580CD78D3E09CEBE1E45DACB42CFEA62
}
}: false,
PeerId{
address: SocketAddrHost{
host: "100.112.24.100",
port: 1347
},
public_key: {
digest: ed25519,
payload: ed0120B71E8ABEB649763813310D9E1EDCE1DA74D129BD68086BE55A5103DF64610358
}
}: false,
PeerId{
address: SocketAddrHost{
host: "alpha.openspacenetwork.org",
port: 1338
},
public_key: {
digest: ed25519,
payload: ed012008215485C4444E69146B9E173CE57604A60883DCD67FD7A11ED10B54EFFE89C8
}
}: true
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: