Bootnodes with unexpected peer IDs

Support
1

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?

2

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!

3

Hey @jim-counter ,

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

2 Likes
4

This error is still persisting with the arm build

1 Like
5

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.

6

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

Screenshot from 2022-11-29 09-06-41
Screenshot from 2022-11-29 09-06-411636×1975 678 KB

7

Mind posting your launch configuration?

8

sure no problem

Screenshot from 2022-11-29 09-45-47
Screenshot from 2022-11-29 09-45-471912×1251 532 KB

9

Same thing I have, when tried to start old but reset node.

The situation:

Screenshot 2022-12-11 at 21.43.46
Screenshot 2022-12-11 at 21.43.461920×1012 271 KB

The starting part:

Screenshot 2022-12-11 at 21.44.28
Screenshot 2022-12-11 at 21.44.281920×1012 231 KB

The composer yaml:

version: "3.7"
services:
  node:
    # For running on Aarch64 add `-aarch64` after `DATE`
    # image: ghcr.io/subspace/node:gemini-2a-2022-sep-10
    image: ghcr.io/subspace/node:gemini-2a-2022-oct-06
    #image: ghcr.io/subspace/node:gemini-3a-2022-dec-01
    volumes:
# Instead of specifying volume (which will store data in `/var/lib/docker`), you can
# alternatively specify path to the directory where files will be stored, just make
# sure everyone is allowed to write there
      - node-data:/var/subspace:rw
      # - /media/hdd2tb/root/subspace:/var/subspace:rw
    ports:
# If port 30333 is already occupied by another Substrate-based node, replace all
# occurrences of `30333` in this file with another value
      - "0.0.0.0:30333:30333"
    restart: unless-stopped
    command: [
      "--chain", "gemini-2a",
      "--base-path", "/var/subspace",
      "--execution", "wasm",
      "--state-pruning", "archive",
      "--port", "30333",
      "--rpc-cors", "all",
      "--rpc-methods", "safe",
      "--unsafe-ws-external",
      "--validator",
# Replace `INSERT_YOUR_ID` with your node ID (will be shown in telemetry)
      "--name", "da_blockchain1"
    ]
    healthcheck:
      timeout: 5s
# If node setup takes longer then expected, you want to increase `interval` and `retries` number.
      interval: 30s
      retries: 5

  farmer:
    depends_on:
      node:
        condition: service_healthy
    # For running on Aarch64 add `-aarch64` after `DATE`
    # image: ghcr.io/subspace/farmer:gemini-2a-2022-sep-10
    image: ghcr.io/subspace/farmer:gemini-2a-2022-oct-06
    #image: ghcr.io/subspace/farmer:gemini-3a-2022-dec-01
    volumes:
# Instead of specifying volume (which will store data in `/var/lib/docker`), you can
# alternatively specify path to the directory where files will be stored, just make
# sure everyone is allowed to write there
     - farmer-data:/var/subspace:rw
     # - /media/hdd2tb/root/subspace:/var/subspace:rw
    ports:
# Un-comment following line to unlock farmer's RPC
#      - "127.0.0.1:9955:9955"
# If port 40333 is already occupied by something else, replace all
# occurrences of `40333` in this file with another value
      - "0.0.0.0:40333:40333"
    restart: unless-stopped
    command: [
      "--base-path", "/var/subspace",
      "farm",
      "--node-rpc-url", "ws://node:9944",
      "--ws-server-listen-addr", "0.0.0.0:9955",
      "--listen-on", "/ip4/0.0.0.0/tcp/40333",
# Replace `WALLET_ADDRESS` with your Polkadot.js wallet address
      "--reward-address", "st8oy5JBzAZLZR4TCWEnJmy7aAe9yHij3DB2w8ZLKK4MJvTtH",
      "--plot-size", "100G"
    ]
volumes:
  node-data:
  farmer-data: