This article contains information about manually terminating the nstrace processes on a NetScaler appliance.
When simultaneously recording multiple network packet trace files on a NetScaler appliance, it might not be possible to terminate all trace files. For example, you might notice some issues in using the configuration utility or the client connection to the appliance might terminate. Recording a trace file on an appliance starts the following processes, which you can display from the shell prompt:
/netscaler/nstraceaggregator
/bin/sh /netscaler/nstrace.sh
You can run the following command to terminate the process of recording a trace file:
nstrace.sh –stop
If the preceding command fails, you might have to manually terminate the processes.
You need to terminate both processes to stop recording packet traces. If you unintentionally leave a trace process running, the trace file might reach an unmanageable size. These trace files can eventually fill the hard disk space, which might cause irregularities in the appliance behavior.
To terminate the nstrace processes, complete the following procedure:
To terminate the processes, you require the respective nstrace process IDs. Run the following command from the shell prompt to display the process IDs:
ps –auxwww | grep nstrace or
ps aux | grep -i trace from shell prompt
In the output of the preceding command, note the process IDs of the /netscaler/nstraceaggregator and /bin/sh /netscaler/nstrace.sh processes, as shown in the following screen shot:
Run the following command to terminate the /bin/sh /netscaler/nstrace.sh process:
kill 93101
Note: If you choose to terminate the /netscaler/nstraceaggregator process before terminating the /bin/sh /netscaler/nstrace.sh process, the nstrace.sh process automatically restarts. Therefore, it is advisable to terminate the /bin/sh /netscaler/nstrace.sh process before terminating the /netscaler/nstraceaggregator process.
Run the following command to terminate the /netscaler/nstraceaggregator process:
kill 93113