SOLO-3006

NodeJfrPidNotFoundSoloError

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.

Troubleshooting Steps

1. Verify the consensus node is running inside the pod: kubectl exec – ps axww -o pid,command
2. Check node startup logs: kubectl logs -n
3. Restart the node if ServicesMain is absent: solo consensus node restart