PeerManager().SelectPeers returns peer which don't support the protocol

[kaichaosun]

I'm trying to use PeerManager SelectPeers for store.StoreQueryID_v300, it returned a peer id and using it for the hash query, got error:

store.queryByHash failed                 requestID=0x28af3edd739b2acbfbfd7c915445cfd0c3ba0a04956258dae5b6203738b7f6b9 error="failed to negotiate protocol: protocols not supported: [/vac/waku/store-query/3.0.0]"

[chaitanyaprem]

That is odd.
Can you provide debug logs for this scenario?
I want to see if the node has advertise Storev3 as part of its identity protocol. Because that is where protocols for peer are stored within peerStore.
Another method is if someone explicitly adds a peer indicating it supports a specific protocol, then also this information is added to peerStore.

[kaichaosun]

The error logs comes from status-im/status-go#5217

log file: https://drive.google.com/file/d/1bKOwZQ6qweBZh4utbRYmDQPCWKyU_NOW/view?usp=sharing
@chaitanyaprem

[chaitanyaprem]

Can you let me know the query to which Store peer has failed?
Because all nodes in the fleets don't have store enabled, and I am not sure if all of them have storev3 enabled as well.

[chaitanyaprem]

One scenario i could think of is this:
ENR of the fleet node or Store node indicates it has store protocol, based on which the local go-waku node is including the peer to support Storev3. But what if fleet node is still using storev2? In that case go-waku thinks node supports Storev3, but actually fleet supports Storev2.
It would help to get details of the peer hence.

[chaitanyaprem]

One scenario i could think of is this: ENR of the fleet node or Store node indicates it has store protocol, based on which the local go-waku node is including the peer to support Storev3. But what if fleet node is still using storev2? In that case go-waku thinks node supports Storev3, but actually fleet supports Storev2. It would help to get details of the peer hence.

I can confirm from your logs that you are using shards.test fleet which is not yet upgraded to latest nwaku release(which means it doesn't support storev2). Hence this is what must be happening, Can you change fleet to shards.staging and confirm if you are still facing this issue?

[kaichaosun]

@chaitanyaprem you can check the peers info here #1098 (comment), it shows store/v3 is there.

[chaitanyaprem]

@chaitanyaprem you can check the peers info here #1098 (comment), it shows store/v3 is there.

Hmm, i do see only 1 node having storev3. I think this node was in the midst of an upgrade and ran into some issues.
I am not sure if the node is working fine now, because looks like something was done to fix the issue on Friday.
Maybe try again today and see. If not, then either @gabrielmer or @richard-ramos will have an idea.

Also, In order for you to be able to proceed without getting blocked by this, you could use shards.staging fleet to verify as well.

[chaitanyaprem]

@kaichaosun are you still seeing this issue?

if not, we can close this.

[kaichaosun]

We can close it for now.