SOLO-3094
NodeContainerCrashedSoloError — Component
NodeContainerCrashedSoloError
| Code | SOLO-3094 |
| Category | Component |
| Ownership | Infrastructure |
| Retryable | No |
Description
Thrown when solo detects that a consensus node’s container has entered a non-recoverable crash state (e.g. CrashLoopBackOff, OOMKilled) while polling for the node to become active. The underlying process will never recover on its own, so solo fails fast instead of exhausting the full polling timeout.
Troubleshooting Steps
- Check node pod status: kubectl get pods -n
-l solo.hedera.com/node-name= - View previous container logs: kubectl logs -n
-l solo.hedera.com/node-name= –previous - Review solo logs: tail -n 100 ~/.solo/logs/solo.log