Component on Solo

SOLO-3001

Mon, 01 Jan 0001 00:00:00 +0000

`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.

SOLO-3003

Mon, 01 Jan 0001 00:00:00 +0000

`NodeBuildUploadFailedSoloError`


Code	`SOLO-3003`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when solo cannot upload the build.zip artifact; the underlying failure is wrapped in cause. solo uploads the packaged build so nodes can be provisioned from it, so this means the upload failed — for example the source file was missing or unreadable, or the destination was unreachable. It is retryable.

Troubleshooting Steps

Review solo logs: tail -n 100 ~/.solo/logs/solo.log
Check node pod status: kubectl get pods -n -l solo.hedera.com/type=network-node
Inspect the pod for more detail: kubectl describe pod -n

SOLO-3004

Mon, 01 Jan 0001 00:00:00 +0000

`NodeBuildCopyFailedSoloError`


Code	`SOLO-3004`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when solo cannot copy a local build into a consensus node; the underlying failure is wrapped in cause. When running with a local platform build, solo copies the build artifacts into the node pod, so this means that copy failed — for example the pod was not reachable, the destination path was not writable, or the connection dropped mid-copy. It is retryable.

SOLO-3005

Mon, 01 Jan 0001 00:00:00 +0000

`NodeJfrExecutionFailedSoloError`


Code	`SOLO-3005`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when a Java Flight Recorder (JFR) operation on a consensus node pod fails; the message names the operation and the pod. solo runs JFR commands inside the node container to capture profiling data, so this means that command failed — for example the pod was not reachable or the command returned an error. It is retryable.

SOLO-3006

Mon, 01 Jan 0001 00:00:00 +0000

`NodeJfrPidNotFoundSoloError`


Code	`SOLO-3006`
Category	Component
Ownership	Solo
Retryable	No

Description

Thrown when solo cannot find the ServicesMain process id inside a consensus node pod; the message names the pod. JFR profiling must attach to the running node process, so this is raised when that process cannot be located — which points to an unexpected container state or a defect in how solo locates the process, and is treated as an internal Solo error.

SOLO-3007

Mon, 01 Jan 0001 00:00:00 +0000

`NodeDebugArchiveFailedSoloError`


Code	`SOLO-3007`
Category	Component
Ownership	Solo
Retryable	No

Description

Thrown when solo cannot create the debug archive it assembles for troubleshooting; the underlying failure is wrapped in cause. The archive bundles a node’s logs and diagnostic data, and reaching this failure points to a problem in solo’s archive-creation logic rather than user or infrastructure input, so it is treated as an internal Solo error and should be reported with the full error output.

SOLO-3008

Mon, 01 Jan 0001 00:00:00 +0000

`BlockNodeConfigFailedSoloError`


Code	`SOLO-3008`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when solo fails while building the block-nodes configuration; the underlying failure is wrapped in cause. solo generates the configuration that tells consensus nodes how to reach the block nodes, so this means that generation step failed — for example required connection details could not be resolved. It is retryable, since a transient resolution problem often clears on a later attempt.

SOLO-3009

Mon, 01 Jan 0001 00:00:00 +0000

`ChartInstallFailedSoloError`


Code	`SOLO-3009`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when solo cannot install a Helm chart; the message names the chart and wraps the underlying failure in cause. solo installs charts to deploy its components, so this means the Helm install failed — for example a bad chart version or values, an image that cannot be pulled, or a cluster that is unreachable or short on resources. It is retryable, since transient registry or cluster issues often clear on a later attempt.

SOLO-3010

Mon, 01 Jan 0001 00:00:00 +0000

`NetworkDestroyFailedSoloError`


Code	`SOLO-3010`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo consensus network destroy cannot tear down the consensus network; the underlying failure is wrapped in cause. Destroy uninstalls the network Helm release and removes its consensus node pods and resources, so this means teardown did not complete — for example a Helm release could not be removed or the cluster API was unreachable.

SOLO-3011

Mon, 01 Jan 0001 00:00:00 +0000

`NodeNotReadySoloError`


Code	`SOLO-3011`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when a consensus node does not reach the expected status within the allotted polling attempts; the message names the node alias, the expected status, and the attempt count (attempt/maxAttempts). solo polls node status while waiting for nodes to come up or change state, and raises this once the attempts are exhausted without the node reaching the expected status — for example the node is crash-looping, stuck during startup, or unable to join the network.

SOLO-3012

Mon, 01 Jan 0001 00:00:00 +0000

`RapidFireExecutionSoloError`


Code	`SOLO-3012`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when a rapid-fire load test step fails to execute; the message describes the failing step and, when present, wraps the underlying cause. Rapid-fire runs load against the network, so this means one of its execution steps did not succeed. It is retryable, since transient cluster or network issues during the test often clear on a later attempt.

SOLO-3013

Mon, 01 Jan 0001 00:00:00 +0000

`NodeStakeTransactionErrorSoloError`


Code	`SOLO-3013`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when a staking transaction fails to execute; when available the underlying failure is wrapped in cause. solo submits staking transactions to configure how accounts and nodes stake, so this means the transaction was rejected or could not be submitted. It is retryable, since a transient network or node-readiness issue often clears on a later attempt.

SOLO-3014

Mon, 01 Jan 0001 00:00:00 +0000

`NodePrepareUpgradeTransactionErrorSoloError`


Code	`SOLO-3014`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when the prepare-upgrade transaction fails to execute; when available the underlying failure is wrapped in cause. This transaction stages the upgrade artifacts on the network before a freeze-upgrade, so this means staging was rejected or could not be submitted — for example the upgrade file was not present or valid, or the network could not be reached. It is retryable.

SOLO-3015

Mon, 01 Jan 0001 00:00:00 +0000

`NodeFreezeUpgradeTransactionErrorSoloError`


Code	`SOLO-3015`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when a freeze-upgrade transaction fails to execute; when available the underlying failure is wrapped in cause. solo submits this transaction to freeze the network in preparation for a software upgrade, so this means it was rejected or could not be submitted — for example the prepared upgrade was not staged, the admin key did not sign, or the network could not be reached. It is retryable.

SOLO-3016

Mon, 01 Jan 0001 00:00:00 +0000

`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.

SOLO-3017

Mon, 01 Jan 0001 00:00:00 +0000

`NodeUpdateTransactionErrorSoloError`


Code	`SOLO-3017`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when the node-update transaction fails to execute; when available the underlying failure is wrapped in cause. solo submits a node-update transaction to change a consensus node’s address-book entry (keys or endpoints), so this means the transaction was rejected or could not be submitted — for example the signing key was wrong, the updated values were invalid, or the network could not be reached.

SOLO-3018

Mon, 01 Jan 0001 00:00:00 +0000

`NodeDeleteTransactionErrorSoloError`


Code	`SOLO-3018`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when the node-delete transaction fails to execute; when available the underlying failure is wrapped in cause. solo submits a node-delete transaction to remove a consensus node from the address book, so this means the transaction was rejected or could not be submitted — for example the admin key did not sign, the target node id was invalid, or the network could not be reached.

SOLO-3019

Mon, 01 Jan 0001 00:00:00 +0000

`NodeCreateTransactionErrorSoloError`


Code	`SOLO-3019`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when the node-create transaction fails to execute; when available the underlying failure is wrapped in cause. solo submits a node-create transaction to add a consensus node to the network’s address book, so this means the transaction was rejected or could not be submitted — for example the admin key did not sign, the node endpoints or parameters were invalid, or the network could not be reached.

SOLO-3021

Mon, 01 Jan 0001 00:00:00 +0000

`AccountBalanceQueryFailedSoloError`


Code	`SOLO-3021`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when solo cannot read an account’s HBAR balance from the network via the Hedera SDK; the message names the account and, when present, wraps the underlying cause. solo queries balances to verify funding and confirm operations, so this is raised when the balance query does not return — typically because the target consensus node is unreachable or not yet ACTIVE, or the SDK client is misconfigured. It is retryable, since a transient network or node-readiness issue often clears on a later attempt.

SOLO-3022

Mon, 01 Jan 0001 00:00:00 +0000

`ExplorerDeployFailedSoloError`


Code	`SOLO-3022`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo explorer node add cannot bring up the Hiero Explorer: the Helm release for the explorer chart failed to install, or its pods never reached a Ready state before solo stopped waiting. The original failure is wrapped in cause.message. Typical roots are an explorer image that cannot be pulled, misconfigured chart values (for example an unreachable mirror-node endpoint), a TLS/cert-manager prerequisite that is not ready, or insufficient cluster resources to schedule the pod.

SOLO-3023

Mon, 01 Jan 0001 00:00:00 +0000

`ExplorerUpgradeFailedSoloError`


Code	`SOLO-3023`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo explorer node upgrade cannot upgrade the Hiero Explorer; the underlying failure is wrapped in cause. Upgrade re-applies the explorer Helm release at a new chart or version, so this means the upgrade did not succeed — for example a Helm failure, an image that cannot be pulled, or misconfigured values.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Inspect Helm release: helm status -n
View explorer pod logs: kubectl logs -n

SOLO-3024

Mon, 01 Jan 0001 00:00:00 +0000

`ExplorerDestroyFailedSoloError`


Code	`SOLO-3024`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo explorer node destroy cannot tear down the Hiero Explorer; the underlying failure is wrapped in cause. Destroy uninstalls the explorer Helm release and removes its resources, so this means that teardown did not complete — for example a Helm release could not be removed or the cluster API was unreachable.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
List Helm releases: helm list -A
Force-uninstall if stuck: helm uninstall -n

SOLO-3025

Mon, 01 Jan 0001 00:00:00 +0000

`RelayDeployFailedSoloError`


Code	`SOLO-3025`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo relay node add cannot deploy the JSON-RPC relay; the underlying failure is wrapped in cause. Deploy installs the relay Helm release, so this means that install did not succeed — for example a Helm failure, an image that cannot be pulled, misconfigured values (such as an unreachable network or mirror-node endpoint), or insufficient cluster resources.

SOLO-3026

Mon, 01 Jan 0001 00:00:00 +0000

`RelayUpgradeFailedSoloError`


Code	`SOLO-3026`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo relay node upgrade cannot upgrade the JSON-RPC relay; the underlying failure is wrapped in cause. Upgrade re-applies the relay Helm release at a new chart or version, so this means the upgrade did not succeed — for example a Helm failure, an image that cannot be pulled, or misconfigured values.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Inspect Helm release: helm status -n
View relay pod logs: kubectl logs -n

SOLO-3027

Mon, 01 Jan 0001 00:00:00 +0000

`RelayDestroyFailedSoloError`


Code	`SOLO-3027`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo relay node destroy cannot tear down the JSON-RPC relay; the underlying failure is wrapped in cause. Destroy uninstalls the relay Helm release and removes its resources, so this means teardown did not complete — for example a Helm release could not be removed or the cluster API was unreachable.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
List Helm releases: helm list -A
Force-uninstall if stuck: helm uninstall -n

SOLO-3028

Mon, 01 Jan 0001 00:00:00 +0000

`RelayNotRunningSoloError`


Code	`SOLO-3028`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when a JSON-RPC relay that should be running is not; the message names the release and wraps the underlying failure in cause. solo checks that the relay pods are present and running before relying on it, so this means that check failed. It is retryable, since a relay that is still starting or briefly restarting often recovers on a later attempt.

SOLO-3029

Mon, 01 Jan 0001 00:00:00 +0000

`RelayNotReadySoloError`


Code	`SOLO-3029`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when a deployed JSON-RPC relay does not become ready in time; the message names the release and wraps the underlying failure in cause. solo waits for the relay pods to reach a Ready state after install, so this means that wait did not succeed in time. It is retryable, since a relay that is merely slow to start often becomes ready on a later attempt; a persistent failure points to a crash-looping or misconfigured relay.

SOLO-3030

Mon, 01 Jan 0001 00:00:00 +0000

`RelayOperatorKeyRetrievalFailedSoloError`


Code	`SOLO-3030`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when solo cannot retrieve the operator key the JSON-RPC relay needs; the underlying failure is wrapped in cause. The relay signs transactions with an operator account key that solo reads (for example from a secret), so this means that retrieval failed. It is retryable, since a transient cluster or lookup problem often clears on a later attempt.

SOLO-3031

Mon, 01 Jan 0001 00:00:00 +0000

`MirrorNodeDeployFailedSoloError`


Code	`SOLO-3031`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo mirror node add cannot deploy the mirror node; the underlying failure is wrapped in cause. Deploy installs the mirror node Helm release (its importer, REST, and database components), so this means that install did not succeed — for example a Helm failure, an image that cannot be pulled, misconfigured values, or insufficient cluster resources.

SOLO-3032

Mon, 01 Jan 0001 00:00:00 +0000

`MirrorNodeUpgradeFailedSoloError`


Code	`SOLO-3032`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo mirror node upgrade cannot upgrade the mirror node; the underlying failure is wrapped in cause. Upgrade re-applies the mirror node Helm release at a new chart or version, so this means the upgrade did not succeed — for example a Helm failure, an image that cannot be pulled, or misconfigured values.

SOLO-3033

Mon, 01 Jan 0001 00:00:00 +0000

`MirrorNodeDestroyFailedSoloError`


Code	`SOLO-3033`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo mirror node destroy cannot tear down the mirror node; the underlying failure is wrapped in cause. Destroy uninstalls the mirror node Helm release and removes its resources, so this means teardown did not complete — for example a Helm release could not be removed or the cluster API was unreachable.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
List Helm releases: helm list -A
Force-uninstall if stuck: helm uninstall -n

SOLO-3034

Mon, 01 Jan 0001 00:00:00 +0000

`MirrorNodeOperatorKeyRetrievalFailedSoloError`


Code	`SOLO-3034`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when solo cannot retrieve the operator key the mirror node needs; the underlying failure is wrapped in cause. solo reads the operator account key (for example from a secret) so the mirror node can perform its operations, so this means that retrieval failed. It is retryable, since a transient cluster or lookup problem often clears on a later attempt.

SOLO-3035

Mon, 01 Jan 0001 00:00:00 +0000

`OneShotDeployFailedSoloError`


Code	`SOLO-3035`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when a one-shot deployment fails; the message describes the failing step and wraps the underlying failure in cause. One-shot mode brings up a complete network in a single command by running many deploy steps in sequence, so this means one of those steps did not succeed — the message identifies which, and common roots are Helm, image, or cluster-resource problems in the underlying step.

SOLO-3036

Mon, 01 Jan 0001 00:00:00 +0000

`OneShotDestroyFailedSoloError`


Code	`SOLO-3036`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when destroying a one-shot deployment fails; the underlying failure is wrapped in cause. One-shot destroy tears down everything a one-shot deploy created, so this means that teardown did not complete — for example a Helm release or cluster could not be removed, or the cluster API was unreachable.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
List remaining Helm releases: helm list -A
Delete stuck resources manually: kubectl delete -n

SOLO-3037

Mon, 01 Jan 0001 00:00:00 +0000

`OneShotDeploymentInfoRetrievalFailedSoloError`


Code	`SOLO-3037`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot retrieve information about a one-shot deployment; the underlying failure is wrapped in cause. solo reads deployment details (such as component status and endpoints) to report them, so this means that lookup failed — for example the cluster was unreachable or the expected resources were not found.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Verify kubeconfig context is valid: kubectl cluster-info

SOLO-3038

Mon, 01 Jan 0001 00:00:00 +0000

`FalconValuesPreparationFailedSoloError`


Code	`SOLO-3038`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot prepare the Falcon values file used during deployment; the underlying failure is wrapped in cause. solo assembles this Helm values file from configuration and runtime inputs before installing, so this means that preparation step failed — for example a required input was missing or invalid, or the file could not be written.

SOLO-3039

Mon, 01 Jan 0001 00:00:00 +0000

`BlockNodeDeployFailedSoloError`


Code	`SOLO-3039`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo block node add cannot deploy a block node; the underlying failure is wrapped in cause. Deploy installs the block node Helm release, so this means that install did not succeed — for example a Helm failure, an image that cannot be pulled, misconfigured values, or insufficient cluster resources.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Inspect block node pods: kubectl get pods -A -l block-node.hiero.com/type=block-node
Inspect Helm release: helm status -n
Check Helm history: helm history -n

SOLO-3040

Mon, 01 Jan 0001 00:00:00 +0000

`BlockNodeDestroyFailedSoloError`


Code	`SOLO-3040`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo block node destroy cannot tear down a block node; the underlying failure is wrapped in cause. Destroy uninstalls the block node Helm release and removes its resources, so this means teardown did not complete — for example a Helm release could not be removed or the cluster API was unreachable.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Inspect block node pods: kubectl get pods -A -l block-node.hiero.com/type=block-node
Inspect Helm release: helm status -n
Check Helm history: helm history -n

SOLO-3041

Mon, 01 Jan 0001 00:00:00 +0000

`BlockNodeUpgradeFailedSoloError`


Code	`SOLO-3041`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo block node upgrade cannot upgrade a block node; the underlying failure is wrapped in cause. Upgrade re-applies the block node Helm release at a new chart or version, so this means the upgrade did not succeed — for example a Helm failure, an image that cannot be pulled, or misconfigured values.

SOLO-3042

Mon, 01 Jan 0001 00:00:00 +0000

`BlockNodeAddExternalFailedSoloError`


Code	`SOLO-3042`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot register an external block node with the deployment; the underlying failure is wrapped in cause. Adding an external block node records a block node that runs outside this deployment so consensus nodes can use it, so this means that registration step failed — for example the provided endpoint was unreachable or the remote configuration could not be updated.

SOLO-3043

Mon, 01 Jan 0001 00:00:00 +0000

`BlockNodeDeleteExternalFailedSoloError`


Code	`SOLO-3043`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot remove an external block node from the deployment; the underlying failure is wrapped in cause. Removing an external block node updates the configuration so consensus nodes no longer use it, so this means that removal step failed — for example the remote configuration could not be updated.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Inspect the remote config for the registered node: solo deployment config info
Inspect block node pods: kubectl get pods -A -l block-node.hiero.com/type=block-node
If the issue persists, report it with your solo log

SOLO-3044

Mon, 01 Jan 0001 00:00:00 +0000

`BlockNodeHealthCheckFailedSoloError`


Code	`SOLO-3044`
Category	Component
Ownership	Infrastructure
Retryable	Yes

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.

SOLO-3045

Mon, 01 Jan 0001 00:00:00 +0000

`RapidFireLoadStartFailedSoloError`


Code	`SOLO-3045`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when solo cannot start a rapid-fire load run; the underlying failure is wrapped in cause. This step launches the load generator against the network, so this means startup failed — for example the load-test workload could not be created or scheduled. It is retryable, since transient cluster issues often clear on a later attempt.

SOLO-3046

Mon, 01 Jan 0001 00:00:00 +0000

`RapidFireLoadStopFailedSoloError`


Code	`SOLO-3046`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot stop a rapid-fire load run; the underlying failure is wrapped in cause. This step halts the running load generator, so this means the stop did not succeed — for example the workload could not be reached or removed.

Troubleshooting Steps

Check solo logs for the root cause: tail -n 100 ~/.solo/logs/solo.log
Check NLG pod status: kubectl get pods -n -l app.kubernetes.io/instance=network-load-generator
Check for running NLG Java processes: kubectl exec -n – ps aux | grep java
To force-stop, uninstall the NLG chart: helm uninstall network-load-generator -n

SOLO-3047

Mon, 01 Jan 0001 00:00:00 +0000

`RapidFireKillFailedSoloError`


Code	`SOLO-3047`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot stop a running rapid-fire load test; the message names the test class and wraps the underlying failure in cause. This step terminates the load generator, so this means the stop did not succeed — for example the load-test pod or process could not be reached or signaled.

Troubleshooting Steps

Check if the test process is still running: kubectl exec -n – ps aux | grep
Manually kill the process: kubectl exec -n – pkill -f
To stop the load test entirely, uninstall the NLG chart: helm uninstall network-load-generator -n

SOLO-3048

Mon, 01 Jan 0001 00:00:00 +0000

`AccountCreationFailedSoloError`


Code	`SOLO-3048`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when creating a Hedera account through the SDK fails; the underlying failure is wrapped in cause. solo creates accounts (for example operator or treasury accounts) during network setup, so this means the create transaction did not succeed — commonly because the network rejected it (insufficient payer balance, key problems) or the consensus node could not be reached.

SOLO-3049

Mon, 01 Jan 0001 00:00:00 +0000

`AccountKeyUpdateFailedSoloError`


Code	`SOLO-3049`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when updating the keys on a Hedera account fails; the message names the account. solo rotates account keys (for example replacing genesis keys) with an update transaction, so this means that transaction did not succeed — commonly because the existing key did not sign correctly, the new key is invalid, or the network rejected or could not be reached.

SOLO-3050

Mon, 01 Jan 0001 00:00:00 +0000

`AccountKeysBatchUpdateFailedSoloError`


Code	`SOLO-3050`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when a batch key-update over several accounts does not fully succeed; the message reports how many accounts were not updated. solo updates account keys in bulk during setup and raises this when one or more of those updates is rejected — typically due to signing or key problems on the affected accounts, or transient network failures while submitting the batch.

SOLO-3051

Mon, 01 Jan 0001 00:00:00 +0000

`AccountTransferFailedSoloError`


Code	`SOLO-3051`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when an HBAR transfer transaction fails; the underlying failure is wrapped in cause. solo transfers HBAR to fund accounts during setup and account operations, so this means the transfer was rejected or could not be submitted — commonly an insufficient sender balance, a signing problem, or an unreachable consensus node.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Verify consensus nodes are running: kubectl get pods -n
Verify the sender account has sufficient HBAR balance

SOLO-3052

Mon, 01 Jan 0001 00:00:00 +0000

`AccountInfoFailedSoloError`


Code	`SOLO-3052`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot retrieve an account’s information from the network via the SDK; the underlying failure is wrapped in cause. It means the account-info query did not return — for example the account does not exist, the consensus node is unreachable or not yet ACTIVE, or the SDK client is misconfigured.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Verify consensus nodes are running: kubectl get pods -n
Verify the account ID exists on the network

SOLO-3053

Mon, 01 Jan 0001 00:00:00 +0000

`AccountUpdateFailedSoloError`


Code	`SOLO-3053`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when updating a Hedera account’s properties fails; the message names the account. solo submits an account-update transaction to change account settings, so this means that transaction did not succeed — for example the account’s key did not sign, the requested change was invalid, or the network rejected or could not be reached.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Verify consensus nodes are running: kubectl get pods -n
Verify the account exists on the network: solo ledger account update

SOLO-3054

Mon, 01 Jan 0001 00:00:00 +0000

`AccountSecretCreationFailedSoloError`


Code	`SOLO-3054`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot store an account’s key material as a Kubernetes secret; the message names the account. After creating or updating an account, solo persists its keys in a cluster secret so other components can use them, so this is raised when that secret cannot be created — for example the namespace is missing, a conflicting secret exists, or the Kubernetes API rejected the request.

SOLO-3055

Mon, 01 Jan 0001 00:00:00 +0000

`EvmAddressRetrievalFailedSoloError`


Code	`SOLO-3055`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot determine the EVM address associated with a Hedera account; the message names the account. solo derives or looks up the account EVM (alias) address for EVM-compatible workflows, so this is raised when that lookup fails — for example the account has no EVM address, or its account info could not be retrieved from the network.

SOLO-3056

Mon, 01 Jan 0001 00:00:00 +0000

`NodeAccessConfigFailedSoloError`


Code	`SOLO-3056`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot configure access to a consensus node; the underlying failure is wrapped in cause. This step establishes the connection (such as a port-forward) and credentials needed to reach a node, so this means that configuration failed — for example the node pod or service was not reachable, or a required port-forward could not be created.

SOLO-3057

Mon, 01 Jan 0001 00:00:00 +0000

`NodeClientLoadFailedSoloError`


Code	`SOLO-3057`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot load the Hedera SDK client used to talk to the network; the underlying failure is wrapped in cause. The client is built from network and node connection details plus operator credentials, so this means that load step failed — for example the node services or endpoints could not be resolved, or the operator key was missing or invalid.

SOLO-3058

Mon, 01 Jan 0001 00:00:00 +0000

`NodeClientRefreshFailedSoloError`


Code	`SOLO-3058`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot refresh the Hedera SDK client’s view of the network; the underlying failure is wrapped in cause. solo refreshes the client when the network’s nodes or endpoints change, so this means re-resolving the connection details failed — for example node services could not be retrieved or the new endpoints were unreachable.

SOLO-3059

Mon, 01 Jan 0001 00:00:00 +0000

`NodeClientSetupFailedSoloError`


Code	`SOLO-3059`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot set up the Hedera SDK client for the network; the underlying failure is wrapped in cause. Setup wires the client to the network node endpoints and operator account before any SDK calls, so this means that configuration step failed — for example endpoints could not be resolved or operator credentials were missing or invalid.

SOLO-3060

Mon, 01 Jan 0001 00:00:00 +0000

`SdkPingFailedSoloError`


Code	`SOLO-3060`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when solo SDK ping to a network node does not succeed within the allowed retries; the message names the node alias and the number of retries tried. solo pings nodes to confirm they are reachable and responsive before relying on them, and raises this once retries are exhausted. It is retryable because a node that is merely slow to start often responds on a later attempt; a persistent failure points to a node that is down or unreachable.

SOLO-3061

Mon, 01 Jan 0001 00:00:00 +0000

`NodeServicesRetrievalFailedSoloError`


Code	`SOLO-3061`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot retrieve the Kubernetes services for the network’s consensus nodes; the underlying failure is wrapped in cause. solo reads these services to discover node endpoints, so this means the lookup failed — for example the namespace is wrong, the services do not exist yet, or the Kubernetes API was unreachable.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
List Kubernetes services in the namespace: kubectl get svc -n
Verify consensus nodes are deployed: kubectl get pods -n

SOLO-3062

Mon, 01 Jan 0001 00:00:00 +0000

`GossipKeySecretCreationFailedSoloError`


Code	`SOLO-3062`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot store a consensus node’s gossip keys as a Kubernetes secret; the message names the node alias. Gossip keys secure node-to-node communication and are mounted from a cluster secret, so this means that secret could not be created — for example the namespace is missing, a conflicting secret exists, or the Kubernetes API rejected the request.

SOLO-3063

Mon, 01 Jan 0001 00:00:00 +0000

`TlsKeySecretCreationFailedSoloError`


Code	`SOLO-3063`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot store a generated TLS key as a Kubernetes secret; when available the underlying failure is wrapped in cause. solo persists TLS keys in cluster secrets so components can mount them, so this means the secret could not be created — for example the namespace is missing, a conflicting secret exists, or the Kubernetes API rejected the request.

SOLO-3064

Mon, 01 Jan 0001 00:00:00 +0000

`TlsKeyGenerationFailedSoloError`


Code	`SOLO-3064`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot generate a TLS key; the message includes the underlying error text. solo generates TLS keys to secure node communication, so this means generation failed — for example the key-generation tooling errored or a working file could not be written.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Verify required key generation tools are available
Re-run node setup: solo consensus node setup

SOLO-3065

Mon, 01 Jan 0001 00:00:00 +0000

`SigningKeyGenerationFailedSoloError`


Code	`SOLO-3065`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot generate a node signing key; the underlying failure is wrapped in cause. Signing keys establish a consensus node identity, so this means generation failed — for example the key-generation tooling errored or a working file could not be written.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Verify key generation tools are available
Re-run key generation: solo keys consensus

SOLO-3066

Mon, 01 Jan 0001 00:00:00 +0000

`GrpcTlsKeyGenerationFailedSoloError`


Code	`SOLO-3066`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot generate the gRPC TLS key for a consensus node; the underlying failure is wrapped in cause. solo generates this key to secure node gRPC traffic, so this means key generation failed — for example the key-generation tooling errored or a working file could not be written.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Verify key generation tools are available
Re-run node setup: solo consensus node setup

SOLO-3067

Mon, 01 Jan 0001 00:00:00 +0000

`GrpcTlsCertMismatchSoloError`


Code	`SOLO-3067`
Category	Component
Ownership	User
Retryable	No

Description

Thrown when the gRPC TLS certificate and key supplied by the user do not correspond; the message lists the certificate and key paths. solo pairs each provided certificate with its key for node gRPC TLS, so this means the structures do not match — typically a certificate and key from different pairs, or paths that were swapped or point to the wrong files.

SOLO-3068

Mon, 01 Jan 0001 00:00:00 +0000

`GrpcWebTlsCertMismatchSoloError`


Code	`SOLO-3068`
Category	Component
Ownership	User
Retryable	No

Description

Thrown when the gRPC Web TLS certificate and key supplied by the user do not correspond; the message lists the certificate and key paths. solo pairs each provided certificate with its key for the node’s gRPC Web TLS, so this means the structures do not match — typically a certificate and key from different pairs, or paths that were swapped or point to the wrong files.

SOLO-3069

Mon, 01 Jan 0001 00:00:00 +0000

`CertificateSecretCreationFailedSoloError`


Code	`SOLO-3069`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot create the TLS certificate secret for a consensus node; the message names the node alias. solo stores node certificates as Kubernetes secrets so they can be mounted, so this means the secret could not be created — for example the namespace is missing, a conflicting secret exists, or the Kubernetes API rejected the request.

SOLO-3070

Mon, 01 Jan 0001 00:00:00 +0000

`CertificateParsingFailedSoloError`


Code	`SOLO-3070`
Category	Component
Ownership	User
Retryable	No

Description

Thrown when solo cannot parse a certificate input the user provided; the message names the input, its type, and the line and index of the offending entry. solo parses each supplied certificate to validate and use it, so this means the content is not valid for the expected format — for example a malformed or truncated certificate, or the wrong kind of file supplied.

SOLO-3071

Mon, 01 Jan 0001 00:00:00 +0000

`CertificateFileNotFoundSoloError`


Code	`SOLO-3071`
Category	Component
Ownership	User
Retryable	No

Description

Thrown when a certificate file the user referenced does not exist at the given path; the message names the path and input type, with the line and index of the offending entry. solo reads certificate files from the paths provided on the command line or in configuration, so this means the file is missing or the path is wrong — for example a typo, a relative path resolved from an unexpected directory, or a file that was moved.

SOLO-3072

Mon, 01 Jan 0001 00:00:00 +0000

`ExplorerTlsSecretCreationFailedSoloError`


Code	`SOLO-3072`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot create the TLS certificate secret used by the Hiero Explorer; when available the underlying failure is wrapped in cause. The explorer is served over TLS using a certificate stored as a Kubernetes secret, so this means that secret could not be created — for example the namespace is missing, a conflicting secret exists, or the Kubernetes API rejected the request.

SOLO-3073

Mon, 01 Jan 0001 00:00:00 +0000

`PlatformFileNotFoundSoloError`


Code	`SOLO-3073`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when a platform file solo needs does not exist; the message names the path. solo reads platform artifacts from expected locations during setup, so this means the file is missing — for example the platform build was incomplete, an earlier download or extract step did not produce it, or the path is wrong.

SOLO-3074

Mon, 01 Jan 0001 00:00:00 +0000

`PlatformFileCopyFailedSoloError`


Code	`SOLO-3074`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot copy platform files into a consensus node pod; the message names the source files, the pod, and the destination directory, and wraps the underlying failure in cause. solo copies platform artifacts into the node container during setup, so this means the copy failed — for example the pod was not reachable, the destination path was not writable, or the connection dropped mid-copy.

SOLO-3075

Mon, 01 Jan 0001 00:00:00 +0000

`PlatformKeyFileMissingSoloError`


Code	`SOLO-3075`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when a required key file is missing; the message names the file. solo expects certain key files to be present when provisioning a node, so this means one of them was not found — for example key generation did not produce it, or it was not copied into the expected location.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Verify the key file exists at:
Re-generate keys if needed: solo keys consensus
Re-run node setup: solo consensus node setup

SOLO-3076

Mon, 01 Jan 0001 00:00:00 +0000

`GenesisAdminKeySecretFailedSoloError`


Code	`SOLO-3076`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot store a genesis account’s admin key as a Kubernetes secret; the message names the account. During genesis setup solo persists admin keys in cluster secrets for later use, so this is raised when that secret cannot be created — for example the namespace is missing, a conflicting secret exists, or the Kubernetes API rejected the request.

SOLO-3077

Mon, 01 Jan 0001 00:00:00 +0000

`GenesisDataGenerationFailedSoloError`


Code	`SOLO-3077`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo fails to generate the genesis data used to bootstrap a new network; the underlying failure is wrapped in cause. Genesis generation produces the initial accounts, keys, and configuration the network starts from, so this means that generation step did not complete — for example required inputs were missing or invalid, or a file could not be written.

SOLO-3078

Mon, 01 Jan 0001 00:00:00 +0000

`PostgresInitScriptCopyFailedSoloError`


Code	`SOLO-3078`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo cannot copy the mirror node Postgres initialization script into its container; the message names the namespace and wraps the underlying failure in cause. solo copies this script into the database container before running it, so this means the copy failed — for example the target container or pod was not reachable, or the destination was not writable.

SOLO-3079

Mon, 01 Jan 0001 00:00:00 +0000

`PostgresInitScriptFailedSoloError`


Code	`SOLO-3079`
Category	Component
Ownership	Infrastructure
Retryable	Yes

Description

Thrown when the mirror node Postgres initialization script fails to run; the message includes the number of attempts made and wraps the underlying failure. solo runs this script to initialize the mirror node database, so this means execution did not succeed across the attempts tried — for example the database was not ready or the script returned an error. It is retryable, since a database that is still starting often accepts the script on a later attempt.

SOLO-3080

Mon, 01 Jan 0001 00:00:00 +0000

`MirrorPasswordSecretMissingSoloError`


Code	`SOLO-3080`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when the mirror node database owner credential is absent from the expected secret — specifically MIRROR_IMPORTER_DB_OWNER is not present in the mirror-passwords secret. solo reads this secret to obtain the importer’s database owner, so this means the secret exists without the required key, or was not populated as expected during deployment.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Inspect the mirror-passwords secret: kubectl get secret mirror-passwords -n -o jsonpath="{.data}"
Re-deploy the mirror node to recreate secrets: solo mirror node add

SOLO-3081

Mon, 01 Jan 0001 00:00:00 +0000

`FileContentVerificationFailedSoloError`


Code	`SOLO-3081`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo’s verification of a file’s content fails; the message describes what was being verified. solo verifies file content at certain steps to ensure it matches the expected value, so this means that check did not pass — the content was missing, incomplete, or different from what was required.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Verify consensus nodes are running and healthy: kubectl get pods -n
Inspect node logs for errors: kubectl logs -n

SOLO-3082

Mon, 01 Jan 0001 00:00:00 +0000

`HederaFileCreationFailedSoloError`


Code	`SOLO-3082`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when a Hedera File Service create transaction returns a non-success status; the message includes the network status. solo uses the File Service to store artifacts on the network (such as upgrade files), so this means the file create was rejected — the specific status code identifies why, for example a payer or signature problem or an invalid file.

SOLO-3083

Mon, 01 Jan 0001 00:00:00 +0000

`HederaFileUpdateFailedSoloError`


Code	`SOLO-3083`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when a Hedera File Service update transaction returns a non-success status; the message includes the network status. solo updates network-stored files (such as upgrade files) via the File Service, so this means the update was rejected — the specific status code identifies why.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Verify consensus nodes are running: kubectl get pods -n
Consult the Hedera documentation for the meaning of the status code

SOLO-3084

Mon, 01 Jan 0001 00:00:00 +0000

`HederaFileAppendFailedSoloError`


Code	`SOLO-3084`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when a Hedera File Service append transaction returns a non-success status; the message includes the chunk index and the network status. Large files are uploaded in chunks, so this means appending a particular chunk was rejected — the specific status code identifies why, for example a size limit or a payer or signature problem.

SOLO-3085

Mon, 01 Jan 0001 00:00:00 +0000

`NodeStatusEmptyResponseSoloError`


Code	`SOLO-3085`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when a consensus node’s status check returns an empty response. solo queries each node’s status endpoint to determine its state, so an empty reply means the node returned nothing usable — typically because the node is not yet serving its status endpoint, or the request reached a target that is not ready.

Troubleshooting Steps

Check solo logs: tail -n 100 ~/.solo/logs/solo.log
Verify the consensus node pod is running: kubectl get pods -n
Inspect node logs: kubectl logs -n

SOLO-3086

Mon, 01 Jan 0001 00:00:00 +0000

`NodeStatusMissingLineSoloError`


Code	`SOLO-3086`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when a consensus node’s status check response is missing the expected status line. solo parses the status output to read the node’s current state, so this means the response came back but did not contain the line solo needs — usually because the node is still starting and has not produced full status output, or the output format was unexpected.

SOLO-3087

Mon, 01 Jan 0001 00:00:00 +0000

`PredefinedAccountsCreationFailedSoloError`


Code	`SOLO-3087`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when solo fails to create the set of predefined accounts it seeds into a new network; the underlying failure is wrapped in cause. These accounts are created during setup to provide ready-to-use funded accounts, so this means one of those creations did not succeed — commonly a network rejection, a signing or key problem, or an unreachable consensus node.

SOLO-3088

Mon, 01 Jan 0001 00:00:00 +0000

`FileContentMismatchSoloError`


Code	`SOLO-3088`
Category	Component
Ownership	Infrastructure
Retryable	No

Description

Thrown when content read back from the network does not match what solo uploaded. After uploading a file (for example via the Hedera File Service), solo re-reads it and compares, so this means the round-trip verification failed — the stored content differs from what was sent, indicating the upload was incomplete or corrupted.

Troubleshooting Steps

Retry the file upload — transient network issues can cause partial or corrupt writes
Check solo logs for chunk append errors: tail -n 100 ~/.solo/logs/solo.log
Verify consensus nodes are healthy: kubectl get pods -n
Check node logs for transaction errors: kubectl logs -n
Confirm no concurrent process modified the same Hedera file during the upload

SOLO-3089

Mon, 01 Jan 0001 00:00:00 +0000

`NodeServiceNotFoundSoloError`


Code	`SOLO-3089`
Category	Component
Ownership	User
Retryable	No

Description

Thrown when solo cannot resolve the Kubernetes service for a specific consensus node; the message names the node alias. solo expects each node to expose a service it can reach, so this is raised when no matching service is found — typically because the node alias does not correspond to a deployed node, or the selected deployment or namespace does not contain it.