Troubleshoot issues with debug tool
Some tools within the NetBackup Debug Tool Container may fail to execute or return incomplete results when attached to certain pods or nodes. It is recommended to use --profile=sysadmin and --share-processes=true options to have the same privileges as the original container or node.
Perform the following:
- When launching the debug container, ensure that it is configured with elevated privileges and appropriate namespace sharing.
- Push the image to the registry: The debug tool image is not pushed to the container registry by the image‑pushing script and must be pushed manually by the user.
Navigate to the
VRTSk8s-netbackup-<version>/imagesdirectory.Load the debug tool image:
# docker load -i netbackup-debugtool-<version>.tar.gz
Tag the image for registry:
# docker tag localhost/netbackup/debugtool:<version> <registry>/netbackup/debugtool:<version>
Push the image to the registry:
# docker push <registry>/netbackup/debugtool:<version>
- Using the debug tool:
Use the following command to debug a pod:
# kubectl debug pod/<pod name> -it --image=<debugtool image> --target=<conatiner name> -n <namespace> --profile=sysadmin --share-processes=true
For example, # kubectl debug pod/nbu-primary-0 -it --image=nbuk8sreg.azurecr.io/netbackup/debugtool:11.2 --target=nbu-primary -n netbackup --profile=sysadmin --share-processes=true
Note:
When you exit the debug tool container, the container terminates. Running the command again creates and attaches a new debug tool container.
Use the following command to debug a node:
# kubectl debug node/<node name> -it --image=<debugtool image> --profile=sysadmin --share-processes=true
For example, # kubectl debug node/aks-nbuxpool-26991557-vmss00001t -it --image=nbuk8sreg.azurecr.io/netbackup/debugtool:11.2 --profile=sysadmin --share-processes=true