Node id mismatch in logs

Staking & Delegation Operate a Stake Pool
1

In jormungandr logs I found massive amount of logs such as:

Dec 22 09:01:32.529 INFO peer node ID differs from the expected 0878a31531729d56df1e9f13d46f7a00754041e0dd204020, node_id: 7ae1cc1824a88cff16fefa51ff90ac642eee6d5b9d9476af, peer_addr: 35.238.40.34:3000, task: network

That tas apparently answer from pool node I created, but there is a lot of it from other nodes too. Do anyone know why it happens, is it caused by some misconfiguration that can be fixed?

Thanks!

2

are you using the right trusted peer list with the right version of jormungandr?
Have your node worked before?

3

My config had list of trusted peers which was downloaded on 18th December. I changed that to most recent and after some time after restart I noticed this in (other node) logs (my pool ip is 35.238.40.34):

Dec 22 23:02:21.212 INFO connecting to peer, node_id: 5ec5c8769405f7d52109d71133b778072385aa880a1630d4, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:02:21.639 INFO peer node ID differs from the expected 5ec5c8769405f7d52109d71133b778072385aa880a1630d4, node_id: 94c07816159fed007d19276954489c5ad8366fdee2f68641, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:02:25.766 INFO connecting to peer, node_id: 5ec5c8769405f7d52109d71133b778072385aa880a1630d4, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:02:26.221 INFO disconnecting client, node_id: 94c07816159fed007d19276954489c5ad8366fdee2f68641, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:02:26.223 INFO peer node ID differs from the expected 5ec5c8769405f7d52109d71133b778072385aa880a1630d4, node_id: 94c07816159fed007d19276954489c5ad8366fdee2f68641, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:03:27.286 INFO disconnecting client, node_id: 94c07816159fed007d19276954489c5ad8366fdee2f68641, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:04:25.772 INFO connecting to peer, node_id: 94c07816159fed007d19276954489c5ad8366fdee2f68641, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:04:48.499 INFO disconnecting client, node_id: 94c07816159fed007d19276954489c5ad8366fdee2f68641, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:05:25.777 INFO connecting to peer, node_id: 94c07816159fed007d19276954489c5ad8366fdee2f68641, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:05:55.697 INFO disconnecting client, node_id: 94c07816159fed007d19276954489c5ad8366fdee2f68641, peer_addr: 35.238.40.34:3000, task: network

So seems like it helped but raises 2 questions:

  1. Do we need to update trusted peers list everytime it changes here?
  2. Does every jormungadr’s restart generates new node id?

Pool jormungadr’s version is 0.8.3, logs you see here are from ordinary Daedalus Incentivized for Linux which apparently uses jormungadr 0.8.1

Thanks!

After some time I spotted 
Dec 22 23:07:17.635 INFO connecting to peer, node_id: 878a9e5e4728b70449f34ad9649d6a8435ab9391385f4065, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:07:18.115 INFO peer node ID differs from the expected 878a9e5e4728b70449f34ad9649d6a8435ab9391385f4065, node_id: 94c07816159fed007d19276954489c5ad8366fdee2f68641, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:07:47.290 INFO disconnecting client, node_id: 94c07816159fed007d19276954489c5ad8366fdee2f68641, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:11:35.825 INFO connecting to peer, node_id: 7420ab96590981ce188519f30b374cbdceda28cfaf06db16, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:11:36.558 INFO peer node ID differs from the expected 7420ab96590981ce188519f30b374cbdceda28cfaf06db16, node_id: 94c07816159fed007d19276954489c5ad8366fdee2f68641, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:11:37.457 INFO connecting to peer, node_id: 7420ab96590981ce188519f30b374cbdceda28cfaf06db16, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:11:37.901 INFO disconnecting client, node_id: 94c07816159fed007d19276954489c5ad8366fdee2f68641, peer_addr: 35.238.40.34:3000, task: network
Dec 22 23:11:37.903 INFO peer node ID differs from the expected 7420ab96590981ce188519f30b374cbdceda28cfaf06db16, node_id: 94c07816159fed007d19276954489c5ad8366fdee2f68641, peer_addr: 35.238.40.34:3000, task: network
4
  1. I am not 100% sure but it is better to use the latest ones.
  2. do you think that public_id is the node_id? if so, then probably yes according to this
5
  1. Thanks
  2. I will play with that tomorrow and try to set that id

Thank you @laplasz!

6

so just an update - trusted peers are needed to able to bootstrap.
public_id is not recommended to set - it is ok the get random numbers at starting.

7

According to post Prematurely created and distributed blocks? a challenge and response! I am wondering that id mismatch could happen for purpose. How to check which peer responded with network info such node public_id & ip address?