SOLO-3056

NodeAccessConfigFailedSoloError — Component

NodeAccessConfigFailedSoloError

CodeSOLO-3056
CategoryComponent
OwnershipInfrastructure
RetryableNo

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.

Troubleshooting Steps

  1. Check solo logs: tail -n 100 ~/.solo/logs/solo.log
  2. Verify consensus node pods are running: kubectl get pods -n
  3. Check node logs: kubectl logs -n
  4. Restart the consensus node: solo consensus node restart