SOLO-3001
NodeTransactionFailedSoloError — Component
NodeTransactionFailedSoloError
| Code | SOLO-3001 |
| Category | Component |
| Ownership | Infrastructure |
| Retryable | No |
Description
Thrown when a Hedera SDK transaction that solo submitted to a consensus node receives a receipt whose status is not SUCCESS. The error message carries the operation that failed and the raw network status code (for example node create transaction failed with status: INVALID_SIGNATURE). This means the network reached and rejected the transaction rather than failing to deliver it: common causes are a node that has not yet reached ACTIVE during setup, staking, or a network upgrade; an operator/admin key that does not match the account; or an address-book/state precondition that the transaction violated. The specific status code identifies which.
Troubleshooting Steps
- Check the solo logs for details: tail -n 100 ~/.solo/logs/solo.log
- Verify the node pod is running: kubectl get pods -n
-l solo.hedera.com/type=network-node - Consult the Hedera documentation for the meaning of the status code