-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bardock Follower Node not updating after Deploy #860
Comments
I have the same issue CONTAINER_REV=ab3fc9b450d5a2dc5446a290f84e9c093ac08c67
|
We are also facing the same issue Container version = 'ab3fc9b450d5a2dc5446a290f84e9c093ac08c67' Log output from docker logs suzuka-full-node | tail 2024-11-15T07:16:25.143284Z INFO maptos_fin_view::service: Starting maptos-fin-view services at: "0.0.0.0:30733" |
Related to this: #695 |
When we deploy the Bardock Follower Node using teh Ansible script - initially - the node syncs and deploys showing a block height close to movement's deployed bardock endpoint. After some time however as blocks are produced on Bardock - the follower node does not continue to sync and appears to be stuck.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
As new block are produced the follower node should reflect this on its endpoint
Additional context
ab3fc9b450d5a2dc5446a290f84e9c093ac08c67
Log output from
docker logs suzuka-full-node | tail
The text was updated successfully, but these errors were encountered: