You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How to reproduce:
this easer to observe on small testnet chain with only a zebra and komodod node. The komodod node is the listener and th zebra node has its address in the zebra config.
Start komodod node with the -debug=net param, then start a zebra node. Ensure the komodod node receive "getaddr" message and stop the zebra node with ctrl-C and start it again. You may need to do this several times. Eventually you will see that the zebra node started with no connection available.
There is an error if "info" level is enabled for zebra_network: add_initial_peers: zebra_network::peer_set::initialize: an initial peer connection failed successes=0 errors=1 addr=127.0.0.1:17770 e=request timed out
The reason for this error is that komodod, if it has not reached the max connections of 16, regularly calls addrman.Select() to get the next address to try to connect. This Select() call may lock the addrman object for several minutes (!). So any "getaddr" request is put on lock and all the p2p message pump is stopped until the addrman is unlocked.
There is an issue about that in komodo: KomodoPlatform/komodo#423.
The text was updated successfully, but these errors were encountered:
How to reproduce:
this easer to observe on small testnet chain with only a zebra and komodod node. The komodod node is the listener and th zebra node has its address in the zebra config.
Start komodod node with the -debug=net param, then start a zebra node. Ensure the komodod node receive "getaddr" message and stop the zebra node with ctrl-C and start it again. You may need to do this several times. Eventually you will see that the zebra node started with no connection available.
There is an error if "info" level is enabled for zebra_network:
add_initial_peers: zebra_network::peer_set::initialize: an initial peer connection failed successes=0 errors=1 addr=127.0.0.1:17770 e=request timed out
The reason for this error is that komodod, if it has not reached the max connections of 16, regularly calls addrman.Select() to get the next address to try to connect. This Select() call may lock the addrman object for several minutes (!). So any "getaddr" request is put on lock and all the p2p message pump is stopped until the addrman is unlocked.
There is an issue about that in komodo: KomodoPlatform/komodo#423.
The text was updated successfully, but these errors were encountered: