Resolving an issue of failed probes
If a pod is not in a ready state for a long time, the kubectl describe pod/<podname> -n <namespace> command displays the following errors:
Readiness probe failed: The readiness of the external dependencies is not set.
Server setup is still in progress.
Liveness probe failed: bpps command did not list nbwmc process. nbwmc is not alive.
The Primary server is unhealthy.
To resolve an issue of failed probes
- If you are deploying NetBackup on Kubernetes Cluster for the first time, check the installation logs for detailed error.
Use any of the following methods:
Execute the following command in the respective primary server or media server pod and check the logs in
/mnt/nblogs/setup-server.logs:kubectl exec -it -n <namespace> <pod-name> -- /bin/bash
Run the kubectl logs pod/<podname> -n <namespace> command.
- Check pod events for obtaining more details for probe failure using the following command:
kubectl describe pod/<podname> -n <namespace>
Kubernetes will automatically try to resolve the issue by restarting the pod after liveness probe times out.
- Depending on the error in the pod logs, perform the required steps or contact technical support.