Closed sinkingsugar closed 3 years ago
The attestations messages here are fine - the more problematic issues are the RPC error
logs which indicate we're not fully sending data, and the subsequent descoring.
@arnetheduck some updates:
major
Sep 29 23:57:18.144 DEBG Received BlocksByRoot Request returned: 1, requested: 1, peer: 16Uiu2HAmFSvNoxtKJpKCTC9AqKYiRL6zHFVX3SibBR4Cf7f3bUHB
Sep 29 23:57:18.146 DEBG RPC Error score: 0.00, peer_id: 16Uiu2HAmFSvNoxtKJpKCTC9AqKYiRL6zHFVX3SibBR4Cf7f3bUHB, client: Nimbus: version: 0.0.1, os_version: unknown, err: Internal error: Sending responses to closed inbound substream, protocol: beacon_blocks_by_root, service: libp2p
minor:
Sep 30 01:16:12.769 DEBG RPC Error score: -2.66, peer_id: 16Uiu2HAm9tFkvT3ZzGFLMRnQb5FZXbhUR3AyjiHhgKQ7g3Bqm9co, client: Nimbus: version: 0.0.1, os_version: unknown, err: Negotiation timeout, protocol: ping, service: libp2p
So yeah not much to add, will try to trace LH
tl;dr both logs show it's something related to BlocksByRoot
I've asked about this. in terms of LH perspective it would seem that we closed our end of the stream too early.
is this still happening with the latest nimbus?
also, "too early" would need to be more precise: in mplex, are they saying we send the "close" message before the request is through or something else?
Quoting the answer to "how bad is this log"
Its either you closed your end too early or we took to long to respond. We don't penalize very harshly for it We keep track of the time. So if we shouldn't try and respond after the timeout. So it means from our perspective you closed your end of the stream early
I definitely see them still in devel, but might just be my gossip wip branch , Altho this issue is eth2 rpcs no? So not gossip related afaik
Testing via multinet I noticed that we often emit attestations for unknown blocks, by checking Lighthouse logs.
Some extracts here:
and