Synchronization does not start

Issue Report

Environment

  • Operating System: Linux, Ubuntu 20.04
  • CPU Architecture: Intel Xeon E5
  • RAM: 64 GB DDR3
  • Storage: 500 GB SSD
  • Plot Size: 100G
  • Subspace Deployment Method: now - Docker, but tried CLI too

Problem

Steps to reproduce

  1. On Ubuntu 20.04
  2. cd /root/subspace
  3. docker-compose up -d
  4. Observe strange behavior

Expected result

  • Synchronization does not start

What happens instead

[Paste error here]

Hey @user17 can you check your node on telemetry?

No, it is not displayed in telemetry.

@ImmaZoni ive check previous post, something similar has

“Bootnode you are trying to connect to provided a different peer ID”

In both instances the node sorted itself out, but I found no definitive answer.

@jrwashburn had this issue a while back, any insight on what ended up happening for you?

1 Like

Please provide docker-compose.yml you’re using, you may have some parameters that are not recommended and prevent you from joining the network.

I started the node using cli, not via docker.

Well, initial post says you’re using Docker. What CLI command do you use then? If you can provide the full line as text that’d be ideal.

I can tell from the screenshot that you have a docker. What guide did you use?

1 Like

Yes you are right. Completely confused. Since then I have reinstalled several times.

I apologize for the mistake. I have reinstalled the node several times since then.
Now this is my .yaml

version: "3.7"
services:
  node:
    # For running on Aarch64 add `-aarch64` after `DATE`
    image: ghcr.io/subspace/node:gemini-2a-2022-sep-10
    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
#      - /path/to/subspace-node:/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", "DimonusSubs"
    ]
    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
    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
#      - /path/to/subspace-farmer:/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", "st7QL1JssTDqAHnbBsjT1xJvqyg3emojkK1tR4GPRrmHAH6Pt",
      "--plot-size", "100G"
    ]
volumes:
  node-data:
  farmer-data:

Looks fine to me, what logs looks like now?

What does nslookup bootstrap-0.gemini-2a.subspace.network on your machine prints?
Looks like your DNS records are resolving to wrong servers, to the same one in fact, must be DNS configuration issue on your end.

image

That is correct, can you do the same in the container then?:

  1. docker compose exec -it -u root node bash
  2. Inside of container:
    1. apt-get update
    2. apt-get install --no-install-recommends bind9-dnsutils
    3. Now you should be able to run nslookup bootstrap-0.gemini-2a.subspace.network

Then I see no reason for the behavior you observe…

Try to use just one and see if it complains. For that add --bootnodes /dns/bootstrap-0.gemini-2a.subspace.network/tcp/30333/p2p/12D3KooWFhLGQWC2Fbgu4HXhFy5Gpv9WKHb9Ve4FYEsMb221cfyo argument (in docker-compose.yml it’ll be "--bootnodes", "/dns/bootstrap-0.gemini-2a.subspace.network/tcp/30333/p2p/12D3KooWFhLGQWC2Fbgu4HXhFy5Gpv9WKHb9Ve4FYEsMb221cfyo".

That is just the first of the bootnodes already configured by default, but should simplify debugging somewhat.

If that still doesn’t work, try replacing /dns/bootstrap-0.gemini-2a.subspace.network with /ip4/161.35.48.29. If that doesn’t work then someone is intercepting and messing with your network connections.

And let me know what you get.


The situation has not changed

Yeah, that is super weird, I think something is messing with your network connection. Like intercepting and modifying data sent over the network. I’m not sure how though. Maybe anti-virus software or something of that kind, but I don’t think there is anything wrong with Subspace node itself.

You can briefly try connecting via mobile hotspot to rule-out your provider (but don’t keep it like that, it’ll eat all your data) or try disabling anti-virus software temporarily if you have something custom installed.