Open denver-s opened 3 years ago
I have had this issue persistently; I normally bounce the private node to fix it. If you set up prometheus, you will normally get an alert when this happens.
So when I get an alert, I manually restart the node.
I even opened an issue on tezos gitlab related to this, feel free to update it with your details.
For some reason,
private-node
failed to connect topublic-node-0
.To fix this problem I connected to the gcloud shell:
gcloud container clusters get-credentials blockchain --region us-central1 --project <PROJECT_ID> && kubectl exec xtz-tezos-private-baking-node-mynode-<POD_ID> -c tezos-private-node --namespace tezos -it -- /bin/sh
Checked the p2p stat for the node:
(-A is not used since version v8.0)tezos-admin-client -A xtz-tezos-private-baking-node-mynode p2p stat
tezos-admin-client -E http://xtz-tezos-private-baking-node-mynode:8732 p2p stat
So, the private node is connected to public-node-1 (
10.104.3.14:9732
) and the unconnected node is public-node-0 (10.104.2.14:9732
).(-A is not used since version v8.0)tezos-admin-client -A xtz-tezos-private-baking-node-mynode connect address 10.104.2.14:9732
Now the
p2p stat
shows:Hope it can help others!