Skip to content

Commit

Permalink
chore: checkout troubleshooting.
Browse files Browse the repository at this point in the history
  • Loading branch information
l-monninger committed Aug 16, 2024
1 parent 11ca3c8 commit 2076258
Showing 1 changed file with 12 additions and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -43,4 +43,15 @@ WantedBy=multi-user.target

An Ansible script to deploy the above systemd service is available [here](./suzuka-full-node.yml).

This will set up the Movement Node to connect to sync with the `l-monninger/open-network` environment.
This will set up the Movement Node to connect to sync with the `l-monninger/open-network` environment.

## Troubleshooting

### S3 Bucket Error
If you encounter an error reported by the `setup` service for a reject bucket connection, ensure that you are able to access the bucket manually by getting objects via the AWS CLI.

### Invalid Aptos State Error
If you encounter an error reported by the `setup` service for an invalid Aptos state, this likely because the sync has fetched state into an invalid location relative to your Docker Compose application. An Aptos state error will likely be the first one reported. However, it most likely indicates a corruption of all state Perform a hierarchy of checks:
1. Does the directory indicated by the `DOT_MOVEMENT_PATH` contain folders for `maptos`, `maptos-storage`, and `suzuka-da-db`?
2. Does each of these folders have successfully unarchived files? There should be no archives in these folders.
3. Is the host volume mounted correctly? Check the `volumes` section of your Docker Compose file.

0 comments on commit 2076258

Please sign in to comment.