SOLO-5091
BlockNodeBlocksUnavailableSoloError — System
BlockNodeBlocksUnavailableSoloError
| Code | SOLO-5091 |
| Category | System |
| Ownership | Infrastructure |
| Retryable | Yes |
Description
Thrown when a block node does not expose any block above the mirror importer’s last imported block within the wait window; the message names the block number and the wait duration. It is retryable, since the block node may simply still be starting after a restore; a persistent failure points to a consensus node that is not streaming blocks to the block node.
Troubleshooting Steps
- Verify the consensus node is ACTIVE and streaming blocks to the block node
- Check block node logs for the status heartbeat (newestBlock): kubectl logs -A -l app.kubernetes.io/name=block-node
- Re-run: solo config ops bridge-import-gap