local peer id doesn't match on chain node id

[AzorinAZM]

My node has an issue since auto update yesterday, its continuosly restarting and getting this error: [2024-10-22 12:08:59] INFO: Balance of 0xB1D2e3F9b003Df10cf9Eae81eA0FED7Bbd3b08eB is 4.322805540958718 ETH and 251301.805078125 TRAC. [2024-10-22 12:08:59] INFO: blockchain module initialized with implementation: base:84532 [2024-10-22 12:08:59] INFO: All modules initialized! [2024-10-22 12:08:59] TRACE: Identity id: 31 found for wallet: 0xB1D2e3F9b003Df10cf9Eae81eA0FED7Bbd3b08eB on blockchain: base:84532 [2024-10-22 12:08:59] DEBUG: getIdentityId(operational=0xB1D2e3F9b003Df10cf9Eae81eA0FED7Bbd3b08eB) call has been successfully executed; Result: 31; RPC: https://sepolia.base.org/. [2024-10-22 12:09:00] WARN: On blockchain base:84532 for identity id: 31 local peer id: QmbFwLL2KmR6cC2STChiZkRJScDC5WAZK7j3hmWh3afePy doesn't match on chain node id. [2024-10-22 12:09:00] INFO: Identity ID: 31 [2024-10-22 12:09:00] ERROR: Unable to create blockchain profiles. OT-node shutting down... [2024-10-22 12:09:00] INFO: Stopping node... otnode.service: Main process exited, code=exited, status=1/FAILURE otnode.service: Failed with result 'exit-code'. otnode.service: Consumed 8.506s CPU time. otnode.service: Scheduled restart job, restart counter is at 6230.

This first to images are the logs my node was getting when autoupdate happened, then "mica" suggested me to delete from node config the operational wallets and let the first one alone there.

(above) This are the logs after i delete the other operational wallets and only let the first one on the node config.

(bellow) Those are the ones im getting right now when im writting this issue:

I can add that i have been using operational wallets to publish assets on the DKG, i dont know if this should be something to worry about but i let you know in case this is something useful for your investigation

I have openned the same issue report on the dkj.js v8/develop issues https://github.com/OriginTrail/dkg.js/issues/166

[Mihajlo-Pavlovic]

Thanks for reporting this, we will investigate why are you experiencing this error

[AzorinAZM]

Thank you! Let me know if you need some more info

[alien2108]

Just a notice many of us have this same issue

[alien2108]

I did try two set of wallets when first running the node (op+adm pairs) it might be something related to that....just a guess