search

movementlabsxyz / movement

The Movement Network is a Move-based L2 on Ethereum.
Apache License 2.0
71 stars 61 forks source link

Problem with setting up full node #704

Open mattboston opened 4 days ago

mattboston commented 4 days ago

Describe the bug We're trying to standup a full node using the ansible playbook located here https://github.com/movementlabsxyz/movement/blob/main/docs/movement-node/run/ansible/README.md. We're seeing that the systemd file is trying to run the docker compose files from the suzuka-full-node directory, but it's pointing to two files that don't exist.

docker/compose/suzuka-full-node/docker-compose.setup-local.yml
docker/compose/suzuka-full-node/docker-compose.celestia-local.yml

Next, I tried running it manually (not through systemd). I used the following command to start up the containers.

/usr/bin/docker compose --env-file .env \
    -f docker/compose/suzuka-full-node/docker-compose.yml \
    -f docker/compose/suzuka-full-node/docker-compose.local.yml \
    up \
    --force-recreate --remove-orphans

Originally the .env was the following:

REV=70ae3c1ec7957707108d99e48a2010b2528a80df

But have since updated the .env to be the following:

REV=70ae3c1ec7957707108d99e48a2010b2528a80df
CONTAINER_REV=70ae3c1ec7957707108d99e48a2010b2528a80df
DOT_MOVEMENT_PATH=/home/admin/.movement
MAPTOS_CHAIN_ID=250 # change this to the chain id of the network you are running
MOVEMENT_SYNC="follower::mtnet-l-sync-bucket-sync<=>{maptos,maptos-storage,suzuka-da-db}/**" # change to the sync bucket for the network you are running
M1_DA_LIGHT_NODE_CONNECTION_PROTOCOL=https
M1_DA_LIGHT_NODE_CONNECTION_HOSTNAME="m1-da-light-node.testnet.movementlabs.xyz" # changes this to the hostname of the m1_da_light_node_service on network you are running
M1_DA_LIGHT_NODE_CONNECTION_PORT=443
# you may need to provide AWS credentials for the Amazon SDK to properly interact with the sync bucket
# often this will be picked up appropriately if your environment is configured to use AWS
# the bucket has public read access so you may not need to provide credentials
AWS_ACCESS_KEY_ID={redacted}
AWS_SECRET_ACCESS_KEY={redacted}
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

Here's the output of docker ps:

CONTAINER ID   IMAGE                                                                                               COMMAND                   CREATED         STATUS                        PORTS                                                                                          NAMES
eee0e4a18cf8   ghcr.io/movementlabsxyz/suzuka-faucet-service:70ae3c1ec7957707108d99e48a2010b2528a80df              "/app/suzuka-faucet-…"    2 minutes ago   Up About a minute (healthy)   0.0.0.0:30732->30732/tcp, :::30732->30732/tcp                                                  suzuka-faucet-service
d567ac4aa879   ghcr.io/movementlabsxyz/suzuka-full-node:70ae3c1ec7957707108d99e48a2010b2528a80df                   "/app/suzuka-full-no…"    2 minutes ago   Up About a minute (healthy)   0.0.0.0:30731->30731/tcp, :::30731->30731/tcp, 0.0.0.0:30734->30734/tcp, :::30734->30734/tcp   suzuka-full-node
2a4d252d52f8   ghcr.io/movementlabsxyz/m1-da-light-node:70ae3c1ec7957707108d99e48a2010b2528a80df                   "/app/m1-da-light-no…"    2 minutes ago   Up About a minute (healthy)   0.0.0.0:30730->30730/tcp, :::30730->30730/tcp                                                  m1-da-light-node
a0c5f8e9208c   busybox                                                                                             "sh -c 'echo \"Starti…"   2 minutes ago   Up About a minute (healthy)                                                                                                  celestia-light-node
98d0d0a5af8a   ghcr.io/movementlabsxyz/m1-da-light-node-celestia-bridge:70ae3c1ec7957707108d99e48a2010b2528a80df   "/app/m1-da-light-no…"    2 minutes ago   Up About a minute (healthy)   0.0.0.0:26658->26658/tcp, :::26658->26658/tcp                                                  m1-da-light-node-celestia-bridge
a4b03f557447   ghcr.io/movementlabsxyz/m1-da-light-node-celestia-appd:70ae3c1ec7957707108d99e48a2010b2528a80df     "/app/m1-da-light-no…"    2 minutes ago   Up 2 minutes (healthy)        0.0.0.0:9090->9090/tcp, :::9090->9090/tcp, 0.0.0.0:26657->26657/tcp, :::26657->26657/tcp       m1-da-light-node-celestia-appd
ecc610065358   ghcr.io/movementlabsxyz/suzuka-full-node-setup:70ae3c1ec7957707108d99e48a2010b2528a80df             "/app/suzuka-full-no…"    2 minutes ago   Up 2 minutes (healthy)        0.0.0.0:8090->8090/tcp, :::8090->8090/tcp                                                      setup

No matter how long I wait, running "curl http://localhost:30731/v1" shows the same output:

{"chain_id":250,"epoch":"1","ledger_version":"11","oldest_ledger_version":"0","ledger_timestamp":"1729185377088764","node_role":"validator","oldest_block_height":"0","block_height":"4","git_hash":"7a0e210fe29e2c81c378568eba2b467a7ef6a56e"}

I've also attached the log output from running docker compose. full-node.log

l-monninger commented 3 days ago

If you are trying to participate as a follower, please follow the Follower Node docs. The Full Node docs and Ansible script do indeed need to be updated.