SOLO-3060

SdkPingFailedSoloError

Description

Thrown when solo SDK ping to a network node does not succeed within the allowed retries; the message names the node alias and the number of retries tried. solo pings nodes to confirm they are reachable and responsive before relying on them, and raises this once retries are exhausted. It is retryable because a node that is merely slow to start often responds on a later attempt; a persistent failure points to a node that is down or unreachable.

Troubleshooting Steps

1. Check solo logs: tail -n 100 ~/.solo/logs/solo.log
2. Verify the node pod is running: kubectl get pods -n -l solo.hedera.com/node-name=
3. Inspect node logs: kubectl logs -n
4. Check port-forward status: solo deployment refresh port-forwards
5. Restart the node: solo consensus node restart