Closed atif-konasl closed 3 years ago
This happens on archive node when downloading blocks
WARN [06-23|12:29:38.421] Node data write error err="trie node 3b9272…09a1b2 failed with all peers (1 tries, 1 peers)"
@blazejkrzak not only archive node but also for any new full node too. No new node can join existing pandora network now.
There is no slot progression on validator side also:
error="rpc error: code = Unavailable desc = Syncing to latest head, not ready to respond
I think pandora gives status as syncing so no next block production happen
DEBUG[06-28|17:38:45.518] Message handling failed in `snap` peer=ad9cb7b0 err=EOF
DEBUG[06-28|17:38:45.518] Message handling failed in `eth` id=ad9cb7b04d56282b conn=inbound err=EOF
DEBUG[06-28|17:38:45.519] Removing Ethereum peer peer=ad9cb7b0 snap=true
DEBUG[06-28|17:38:45.519] Removing p2p peer peercount=3 id=ad9cb7b04d56282b duration=9.744s req=true err="useless peer"
Possible suspect: StateBloom
.
When peer requests node info it gets empty [][]byte
in response
.
It looks like it occurs when no transactions were present (Not 100% sure, must confirm it at respin)
At this very moment I am able to download blocks for each of the pods on the staging Only difference is that there was 1 transaction (so maybe state has changed and was migrated from cache to db) Altough staging pods have forked each other due to invalid signature at block no 56
I close this issue, because of:
Expected behaviour
Any new node or archive node should sync up with existing running network.
Actual behaviour
When i spin up any archive node and add peer with existing network nodes, it gets warning log like this :
Steps to reproduce the behaviour
Backtrace