You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we're using the ton-http-api to check the node's block number. However, instead of using mytonctrl, we're running the validator-engine by building a Docker image directly. The problem is, it seems like the ton-http-api is fetching the status from a different node, not ours.
Even when we stop the validator-engine container, Grafana still shows that it's fetching the block number.
The node we launched using mytonctrl works fine. The ton-http-api setup and mainnet.json configuration are the same for both, so I'm not sure what could be causing the difference. Could you please help us look into this?
The text was updated successfully, but these errors were encountered:
Currently, we're using the ton-http-api to check the node's block number. However, instead of using mytonctrl, we're running the validator-engine by building a Docker image directly. The problem is, it seems like the ton-http-api is fetching the status from a different node, not ours.
Even when we stop the validator-engine container, Grafana still shows that it's fetching the block number.
The node we launched using mytonctrl works fine. The ton-http-api setup and mainnet.json configuration are the same for both, so I'm not sure what could be causing the difference. Could you please help us look into this?
The text was updated successfully, but these errors were encountered: