Skip to content
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

network/sync: Received notification that was refused earlier by SyncingEngine #6586

Open
lexnv opened this issue Nov 21, 2024 · 1 comment
Open
Labels
I2-bug The node fails to follow expected behavior.

Comments

@lexnv
Copy link
Contributor

lexnv commented Nov 21, 2024

Reproduced on kusama validator. Confirmed at the moment for litep2p, libp2p pending investigation:

ERROR tokio-runtime-worker sync: received notification from 12D3KooWMb8BgRtEXdG2PGK5mve2nYX2uzAYJ6VhnX9i6hAod4mV who had been earlier refused by `SyncingEngine`

Version deployed: version 1.16.1-ca8beaed148

if !self.peers.contains_key(&peer) {
log::error!(
target: LOG_TARGET,
"received notification from {peer} who had been earlier refused by `SyncingEngine`",
);
return;
}

Grafana link: https://grafana.teleport.parity.io/goto/msBvOdnNg?orgId=1

cc @paritytech/sdk-node

@lexnv lexnv added the I2-bug The node fails to follow expected behavior. label Nov 21, 2024
@lexnv lexnv added this to Networking Nov 21, 2024
@dmitry-markin
Copy link
Contributor

This might be introduced by #5737, but let's wait for confirmation with libp2p backend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I2-bug The node fails to follow expected behavior.
Projects
Status: No status
Development

No branches or pull requests

2 participants