Closed twoeths closed 1 year ago
caught 2 other missed IWANT messages with the same message id (to 2 different nodes), Nimbus confirmed they didn't see this message id at the time
grep -e "0xff2cb2265c354d00e4c5fdacd7209d6bc1c65694" -rn beacon-2023-03-08.log
240978708:Mar-08 23:11:36.481[network] debug: 2023-03-08T23:11:36.481Z libp2p:gossipsub IHAVE: Asking from peers 16Uiu2HAkuzih5wCzH4CxKvnZrekrnjeaz48iEgLb5axDxUbfNj61 message id 0xff2cb2265c354d00e4c5fdacd7209d6bc1c65694
240978826:Mar-08 23:11:36.614[network] debug: 2023-03-08T23:11:36.614Z libp2p:gossipsub IHAVE: Asking from peers 16Uiu2HAmThKa44DYZKvYi52z5gKyAkdLydMrEewrYQHGn9Ez64uS message id 0xff2cb2265c354d00e4c5fdacd7209d6bc1c65694
240997946:Mar-08 23:11:48.970[network] debug: 2023-03-08T23:11:48.970Z libp2p:gossipsub peer %s didn't follow up in %s IWANT requests; adding penalty 16Uiu2HAkuzih5wCzH4CxKvnZrekrnjeaz48iEgLb5axDxUbfNj61 0xff2cb2265c354d00e4c5fdacd7209d6bc1c65694
240997947:Mar-08 23:11:48.970[network] debug: 2023-03-08T23:11:48.970Z libp2p:gossipsub peer %s didn't follow up in %s IWANT requests; adding penalty 16Uiu2HAmThKa44DYZKvYi52z5gKyAkdLydMrEewrYQHGn9Ez64uS 0xff2cb2265c354d00e4c5fdacd7209d6bc1c65694
There is no issue with Nimbus for a while so closing this issue
There are some
Iwant
messages from Lodestar to Nimbushowever Nimbus does not see these message ids, both side use "hex" as message id string format