movementlabsxyz / movement

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

Not able to setup the Open Network #668

Open shivamlync opened 1 month ago

shivamlync commented 1 month ago

Describe the bug I am using the current branch l-monninger/syncador-v2 with the latest commit hash

I am facing the below error. Screenshot from 2024-10-08 12-09-37

To Reproduce Steps to reproduce the behavior:

  1. Go to 'this repo
  2. run the command export CONTAINER_REV=316f6bdfd6f6e6970a206d7dbce6eae0ff6c82fc
  3. run the below command
    ansible-playbook --inventory <inventory> --user ubuntu --extra-vars "movement_container_version=${CONTAINER_REV}" --extra-vars "user=ubuntu" docs/movement-node-experimental/l-monninger/open-network/suzuka-full-follower.yml --private-key <pem file for aws>

Expected behavior It should show routes like /v1 or /v1/spec where one can get the current status of the indexer with parameters like chainId, etc.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Additional context Is there any documentation that would help to setup the open network

l-monninger commented 1 month ago

@shivamlync I would use main. Other operators having been working off of 58bce6f44f4bdc69560655b816fa19f90c89c42a.

l-monninger commented 1 month ago

It of course looks like the M1_DA_LIGHT_NODE_CONNECTION_PORT is not provided above, so likely I left the commit you're working off of was in between changes to the Ansible script.