SOLO-3092

SdkClientNoHealthyNodesSoloError

Description

Thrown when the Hedera SDK client reports “failed to find a healthy working node”, meaning the SDK client’s gRPC connections to the consensus network are all marked unhealthy. This refers to the SDK client’s network connectivity, not the consensus node’s platform status — the consensus node itself is often still ACTIVE. The usual culprits are a broken local port-forward tunnel, an HAProxy issue, or a failure in another component whose deployment performs SDK transactions. It is retryable because re-establishing the connection (for example by recreating the port-forward) often resolves it.

Troubleshooting Steps

1. Check solo logs: tail -n 100 ~/.solo/logs/solo.log
2. Verify the consensus node platform status: solo consensus node states –deployment –node-aliases
3. Recreate the port-forwards: solo deployment refresh port-forwards
4. Check the HAProxy pods are running: kubectl get pods -n -l app.kubernetes.io/name=haproxy
5. If the consensus node is ACTIVE, inspect the other components that were being deployed (for example the JSON-RPC relay or mirror node database): kubectl get pods -n