{{page.netscaler-cpx-short}} troubleshooting

How can I view {{page.netscaler-cpx-short}} logs?

You can view {{page.netscaler-cpx-short}} logs using the kubectl logs command if {{page.netscaler-cpx-short}} is deployed with the tty:true option. You can run the following command to display the logs:

Example,

The following is an example of the {{page.netscaler-cpx-short}} pod deployment with the tty:true option:

You can find more boot logs in the /cpx/log/boot.log file of {{page.netscaler-cpx-short}} file system.

Note: To get the pod name, run the kubectl get pods -o wide command.

How can I collect the technical support bundle from {{page.netscaler-cpx-short}}?

You can run the following command on the shell interface of the Kubernetes master node to collect the {{page.netscaler-cpx-short}} technical support bundle:

You can view the technical support bundle in the /var/tmp/support directory of the {{page.netscaler-cpx-short}}’s file system. Use scp or kubectl cp to copy the technical support bundle from {{page.netscaler-cpx-short}} to the desired destination.

Example:

Why is {{page.netscaler-cpx-short}} pod stuck while booting?

You can check the pod status using the kubectl describe pods command. Run the following command to know the pod status:

Example:

If the pod events show that container is started, then you must check the pod logs.

How do I copy files between the {{page.netscaler-cpx-short}} pod and the Kubernetes master node?

It is recommended to use the volume mount feature of docker to mount the /cpx directory to the file system of the host. If a {{page.netscaler-cpx-short}} container exits core-dumps, logs and other important data are available on the mount point.

You can use any one of the following commands to copy files between the {{page.netscaler-cpx-short}} pod and the Kubernetes master node:

kubectl cp: You can run the following command to copy files from pod to node:

Example:

scp: You can use the command to copy files between the {{page.netscaler-cpx-short}} pod and the Kubernetes node. Run the following command to copy files from pod to node. When it prompts for the password, provide the password for the SSH user:

Example:

How do I capture packets on {{page.netscaler-cpx-short}}?

To capture packets on {{page.netscaler-cpx-short}}, launch the shell interface of {{page.netscaler-cpx-short}} using the kubectl exec command. Run the following command to launch the shell interface of the {{page.netscaler-cpx-short}} pod:

Example:

And, run the following command to begin packet capture:

If you want to stop the ongoing packet capture, run the following command:

You can view the packets captured in a .cap file in the /cpx/nstrace/time-stamp directory on the {{page.netscaler-cpx-short}} file system.

Why is the license server not configured even when {{page.netscaler-cpx-short}} is deployed with the LS_IP=<ADM-IP> environment variable?

Ensure that the license server is accessible from the node on which {{page.netscaler-cpx-short}} is deployed. You can use the ping <ADM-IP> command to verify the connectivity from the {{page.netscaler-cpx-short}} node to Citrix ADM.

If Citrix ADM is accessible from the node, then you must verify the license server configuration logs in the /cpx/log/boot.log file. You can also check for license server configuration using the following command on the shell interface of the {{page.netscaler-cpx-short}} pod:

Example:

Why is pooled license not configured on {{page.netscaler-cpx-short}} even after a successful license server configuration on {{page.netscaler-cpx-short}}?

Verify the license configuration logs in the /cpx/log/boot.log file. You can also verify the configured pooled license on {{page.netscaler-cpx-short}} using the following command on the shell interface of the {{page.netscaler-cpx-short}} pod:

Example,

Also, ensure that the required license files are uploaded in the license server. You can also verify the available licenses on the license server once it is successfully configured on {{page.netscaler-cpx-short}} by using the following command. Run the command on the shell interface of {{page.netscaler-cpx-short}} pod:

Example:

Why do NITRO API calls get Connection Refused response from {{page.netscaler-cpx-short}}?

The default port for NITRO APIs is 9080 (unsecure) and 9443 (secure) from the {{page.netscaler-cpx-short}} release 12.1 onwards. Ensure that the NITRO port of {{page.netscaler-cpx-short}} you try to access is exposed on the pod. You can run the kubectl describe command to view the exposed and mapped port of the {{page.netscaler-cpx-short}} container in the {{page.netscaler-cpx-short}} container section:

Example:

Why does the NSPPE process in {{page.netscaler-cpx-short}} consume most of the CPU usage even when there is no or little traffic?

If {{page.netscaler-cpx-short}} is deployed with the CPX_CONFIG=’{“YIELD”:”NO”}' environment variable, the NSPPE process consumes 100 percent CPU usage even when there is no or little traffic. If you want the NSPPE process not to consume the CPU usage, you must deploy {{page.netscaler-cpx-short}} without the CPX_CONFIG=’{“YIELD”:”NO”} environment variable. By default, the NSPPE process in CPX is configured not to hog or consume the CPU usage.

Why is {{page.netscaler-cpx-short}} not listed in Citrix ADM even when it was deployed with the required environment variables for registration with Citrix ADM?

You can find the logs for {{page.netscaler-cpx-short}} registration with Citrix ADM in the /cpx/log/boot.log file on the {{page.netscaler-cpx-short}} file system.

You can verify the accessibility of the Citrix ADM IP address from the {{page.netscaler-cpx-short}} pod using the ping command. Also, ensure that all the required environment variables for Citrix ADM registration are configured for the {{page.netscaler-cpx-short}} container.

Why does cli_script.sh show Invalid user name or password error message after changing the password for nsroot user?

The command cli_script.sh is a wrapper utility for NSCLI on {{page.netscaler-cpx-short}}. It runs the first argument as command string or file path and the second argument is optional which is credentials. If the password for the nsroot user is changed, you need to provide credentials as the second argument to cli_script.sh. You can run the following command to run NSCLI with credentials:

Example: