SOLO-3044

BlockNodeHealthCheckFailedSoloError

Description

Thrown when a block node health check does not pass; the message states the reason. solo health-checks a block node to confirm it is up and serving before relying on it, so this means the check reported the node unhealthy or could not reach it. It is retryable, since a block node that is still starting often passes on a later attempt.

Troubleshooting Steps

1. Check block node pod status: kubectl get pods -A -l block-node.hiero.com/type=block-node
2. Verify liveness endpoint manually: kubectl exec -n – curl http://localhost:/healthz/readyz
3. Check pod logs: kubectl logs -n -l block-node.hiero.com/type=block-node
4. Check solo logs: tail -n 100 ~/.solo/logs/solo.log