No service is started on port 30731 after starting the node

Node Operators
1

Hello, I tried to run the mainnet follower node locally on Ubuntu 22.04 according to the document Run a Follower Node | Movement Network | Movement.

I used version 714831820d78b3910729a194cd0508fa1efd9aa9 and executed nix develop according to the document.

When I executed the commands below, the components started in sequence, but no service started on port 30731. After the code is started, it continues to prompt “Non-leader upsyncing is disabled” and “waiting for next push” from “setup” process.

screenshot
screenshot1920×414 143 KB

source .env
just movement-full-node native build.setup.follower -t=false

The result of curl localhost:30731/v1 was Connection refused.

The contents of my .env file are as follows:

CONTAINER_REV=714831820d78b3910729a194cd0508fa1efd9aa9
DOT_MOVEMENT_PATH=./.movement
MAPTOS_CHAIN_ID=126 # change this to the chain id of the network you are running
MOVEMENT_SYNC="follower::mainnet-l-sync-bucket-sync<=>{default_signer_address_whitelist,maptos,maptos-storage,movement-da-db}/**" # change to the sync bucket for the network you are running
MOVEMENT_DA_LIGHT_NODE_CONNECTION_PROTOCOL=https
MOVEMENT_DA_LIGHT_NODE_CONNECTION_HOSTNAME="m1-da-light-node.testnet.mainnet.movementnetwork.xyz" # change this to the hostname of the Movement DA Light Node service on network you are running
MOVEMENT_DA_LIGHT_NODE_CONNECTION_PORT=443
AWS_ACCESS_KEY_ID=xxxxx
AWS_SECRET_ACCESS_KEY=xxxxx
AWS_DEFAULT_REGION=us-west-1 # change this to match the region of the sync bucket
AWS_REGION=us-west-1 # change this to match the region of the sync bucket

I tried to start the bardock testnet instead, but the same problem occurred. No service started on port 30731.

I made only one change to the movement repository, adding “run” to the movement-full-node code in process-compose/movement-full-node/process-compose.follower.yml. Otherwise, the code will prompt help content when starting movement-full-node, and will not start the service.

My changes are as follows:

from:

  movement-full-node:
    command: |
      movement-full-node
    depends_on:
      movement-celestia-da-light-node:
        condition: process_healthy
    readiness_probe:
      initial_delay_seconds: 10
      exec:
        command: curl http://0.0.0.0:30731

to:

  movement-full-node:
    command: |
      movement-full-node run
    depends_on:
      movement-celestia-da-light-node:
        condition: process_healthy
    readiness_probe:
      initial_delay_seconds: 10
      exec:
        command: curl http://0.0.0.0:30731

Please help me to solve this problem, I guess maybe I miss some configurations.

1 Like
2

This looks correct and the first screenshot is normal what you should get, just some basic queries to get things out of the way:

  • are you running this locally? assuming so since you mentioned using nix
  • are you getting the connection refused when trying to do the curl from a seperate terminal window?
3

Thanks for your reply, regarding your question:

  • are you running this locally? yes
  • are you getting the connection refused when trying to do the curl from a seperate terminal window? yes, I got connection refused from another terminal.
    I thought the result of curl should be something like {“chain_id”:250,“epoch”:“1”,“ledger_version”:“11911340”,“oldest_ledger_version”:“0”,“ledger_timestamp”:“1735833305209312”,“node_role”:“validator”,“oldest_block_height”:“0”,“block_height”:“779058”,“git_hash”:“9dfc8e7a3d622597dfd81cc4ba480a5377f87a41”}, instead of connection refused. Am I understanding it wrong?