SOLO-3016
NodeFreezeTransactionErrorSoloError — Component
NodeFreezeTransactionErrorSoloError
| Code | SOLO-3016 |
| Category | Component |
| Ownership | Infrastructure |
| Retryable | Yes |
Description
Thrown when a freeze-only transaction fails to execute; when available the underlying failure is wrapped in cause. solo submits a freeze-only transaction to pause the network (for example before maintenance), so this means the transaction was rejected or could not be submitted. It is retryable, since a transient network or node-readiness problem often clears on a later attempt.
Troubleshooting Steps
- Verify the node admin key is correct and loaded from the k8s secret.
- Confirm the freeze admin account has the correct operator key set.
- Verify the freeze admin account has sufficient HBAR balance.
- Verify gossip endpoints and gRPC service endpoints are reachable from the network.
- Review solo logs: tail -n 100 ~/.solo/logs/solo.log