Bootnodes with unexpected peer IDs

Noticed this reported a couple of times on Discord now. Itโ€™s definitely apparent on the gemini-2a-2022-oct-06 Docker image.

On running the node, it continually reports these errors:

subspace-node    | 2022-11-04 14:05:41 [PrimaryChain] ๐Ÿ’” The bootnode you want to connect to at `/dns/bootstrap-0.gemini-2a.subspace.network/tcp/30333/p2p/12D3KooWFhLGQWC2Fbgu4HXhFy5Gpv9WKHb9Ve4FYEsMb221cfyo` provided a different peer ID `12D3KooWMFz2P5k1UBeHSLq8UGKMJHwMn5zbehZeiEF6AfxjVbNX` than the one you expect `12D3KooWFhLGQWC2Fbgu4HXhFy5Gpv9WKHb9Ve4FYEsMb221cfyo`.    
subspace-node    | 2022-11-04 14:05:41 [PrimaryChain] ๐Ÿ’” The bootnode you want to connect to at `/dns/bootstrap-1.gemini-2a.subspace.network/tcp/30333/p2p/12D3KooWPBzmEmEiW87qMkroa6DJunbUe5LnCNSQaiaJpJJN266F` provided a different peer ID `12D3KooWDettGb2jviLBc5qmk67pGshGX2a22dtwD2xz3P6TAkCV` than the one you expect `12D3KooWPBzmEmEiW87qMkroa6DJunbUe5LnCNSQaiaJpJJN266F`.    
subspace-node    | 2022-11-04 14:05:41 [PrimaryChain] ๐Ÿ’” The bootnode you want to connect to at `/dns/bootstrap-5.gemini-2a.subspace.network/tcp/30333/p2p/12D3KooWEGgPiMM9WEBCZFNo8EkMDF3p1B47peSeECnrXWmdd3AY` provided a different peer ID `12D3KooWENiAuwtJiQVZBrAanqNrwppGXwhhV9YTVKqsasSG2wCv` than the one you expect `12D3KooWEGgPiMM9WEBCZFNo8EkMDF3p1B47peSeECnrXWmdd3AY`.    
subspace-node    | 2022-11-04 14:05:41 [PrimaryChain] ๐Ÿ’” The bootnode you want to connect to at `/dns/bootstrap-4.gemini-2a.subspace.network/tcp/30333/p2p/12D3KooWMBeJyaYXKZyAjEytdGkqSoQnaVsX1yUoMKxX8F3P5CSa` provided a different peer ID `12D3KooWE83ffAfnQgtkC86LdbwUDQjpJdWSNRCYqt493TmFXver` than the one you expect `12D3KooWMBeJyaYXKZyAjEytdGkqSoQnaVsX1yUoMKxX8F3P5CSa`.    
subspace-node    | 2022-11-04 14:05:41 [PrimaryChain] ๐Ÿ’” The bootnode you want to connect to at `/dns/bootstrap-2.gemini-2a.subspace.network/tcp/30333/p2p/12D3KooWPiumwCZN91fVkPyJ2qvdPbiKPWbD1isK9iECCA1U3LaZ` provided a different peer ID `12D3KooWChmG2Ab7ogeBZhAnUFcgr1BPKQNFmYgFNG83W3ZoFDpq` than the one you expect `12D3KooWPiumwCZN91fVkPyJ2qvdPbiKPWbD1isK9iECCA1U3LaZ`.    

It seems like boot nodes 0, 1, 2 4 and 5 have changed identity. Is this expected? We still have the remaining boot nodes up to 12 available so this error can safely be ignored? Is there a plan to change the identities back to the expected ones?

Yes, we have removed those machines, I think other machines are now running on the same IP addresses, weโ€™ll get it fixed soon, thanks for heads up!

Hey @jim-counter ,

This should be resolved now. Ping back here if you still see this issue

2 Likes

This error is still persisting with the arm build

1 Like

We have sunset some of the bootnodes, so you will still face this error, but in general as long as your are making progress syncing is nothing to be worries about.

but thatโ€™s the thing Iโ€™m not making any progress syncing, I have zero peers and zero upload and download speed.

Mind posting your launch configuration?

sure no problem