Troubleshooting your IBM certified Containerized environment
This section describes how to troubleshoot in your containerized environment.
The troubleshooting steps assumes that Kubectl
command line tool is installed
and configured in your environment.
When you encounter an issue in your containerized environment, run the following checks to assist you with troubleshooting process.
Generic Checks
- Get nodes information and check the status of nodes is
Ready
kubectl get nodes -n <namespace> -o wide
- Review the Persistent Volume and Persistent Volume Claim information and ensure they match with
your deployment YAML
files
kubectl describe pv <pv name> -n <namespace>
- Get the status of the IBM Connect:Direct for Unix containers deployment
job:
kubectl -n <namespace> rollout status deployment/<deployment name> kubectl describe deployment <deployment name> -n <namespace>
-
Get information about the pods after the IBM Connect:Direct for Unix containers have been deployed:
kubectl get pods -n <namespace> -o wide
-
Retrieve the logs for a particular pod
kubectl logs -f <pod name> -c <deployment name> -n <namespace>
-
Get details about a particular pod
kubectl describe pods <pod name> -n <namespace>
Rerun a failed container deployment job
When a container deployment fails investigate the cause and follow the procedure given below over
command line:
- Delete the failed deployment using the below
command
helm delete --purge <release-name>
- Delete the persistent volume
kubectl delete pv <pv-name>
- Delete the secret
kubectl delete secret <secret-name>
- Delete the configMap
kubectl delete configmap <configmap name>
- Manually delete the data present in persistent volume
- Re-run the deployment steps described in Deploying IBM Connect:Direct for UNIX using an IBM Certified Container Software.
View Container logs
- Check the container logs using the
command
kubectl logs -f <pod name> -c <deployment name> -n <namespace>
- From the mapped path on Storage Volume, check the silent installation logs
cdaiLog.txt
inside thework
directory. - IBM Connect:Direct for UNIX traces for PMGR, SMGR or CMGR can be enabled using the
Connect:Direct Web Services. From the mapped path on Storage Volume, check the traces generated
inside the
work
directory. - IBM Connect:Direct for UNIX stats can be checked in the
work
directory inside the mapped path on Storage Volume.