-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Called on_block_announce with a bad PeerId #5592
Comments
Doesn't seem to happen anymore on my Google Cloud node after #5595 🎉 |
This issue is still happening when trying to submit an extrinsic from a light client to a full node. The logs on the client are:
and the logs of the full node
the code to produce these logs is in paritytech/subxt#91 and sunshine-protocol/sunshine#54 and was invoked with the following cli: ./target/release/sunshine-node --base-path /tmp/alice --alice &> /tmp/alice.log
./target/release/sunshine-node --base-path /tmp/bob --bob
cargo run --example reserve_shares_and_watch --features light-client &> /tmp/lightclient.log cc @4meta5 |
Triaging. To be more precise, the issue is that this remote sends a message on the notifications substream before the main substream is open. In other words, it is the sender that misbehaves. I don't really know what could cause this from the top of my head, and if it doesn't cause any bug or misbehaviour I'm tempted to finish #5670, which would fix that issue by design. |
Switching IP networks is a good way to cause these warnings. These warnings are not fatal and eventually go away. |
FYI, getting this error message at every block on every full node when a light client is syncing (so not just when submitting an extrinsic). |
I have this error ( ERROR sync 💔 Called on_block_announce with a bad peer ID) with the new version 8.27 ... me and other people. Can i do anything to fix ? is this a problem for my node? |
same here, got the same error (a lot) 2021-01-13 03:08:17 💤 Idle (46 peers), best: #5748541 (0xccfb…3615), finalized #5748538 (0xcbea…380d), ⬇ 1.0MiB/s ⬆ 937.0kiB> after restarting service everything is ok.. version |
Same. I get this error a lot after upgrading to 0.8.27, it seems harmless and goes away after a restart. |
Same here, running version 0.8.27-2f845699-x86_64-linux-gnu in Azure Container Instance via parity/polkadot:latest 2021-01-25 16:54:08 💤 Idle (51 peers), best: #3499050 (0xffb2…e13b), finalized #3499049 (0x3ea4…71eb), ⬇ 410.1kiB/s ⬆ 174.5kiB/s After restarting, everything seems ok. |
I'm trying to debug this error log being printed at the moment.
For example, here is a selection of logs concerning a faulty peer:
(I made the effort to find all the entries that are possibly relevant to this peer, but the logs are huge and it's not impossible that I have missed some)
(also, feel free to copy-paste these logs for better readability)
It seems to me that:
Qmar25qYxcoLzPuzHDZ9nM7o38mNPqnKrZaksf3aY8rdM8
is established with task ID 48992.The last step seems wrong to me, as the first connection should still be alive. I didn't find anything in the logs about task ID 48992 other than what is above.
cc @romanb is that related to libp2p/rust-libp2p#1546?
The text was updated successfully, but these errors were encountered: