How to collect traces for troubleshooting Kaspersky Endpoint Security for Linux
Show applications and versions that this article concerns
- Kaspersky Endpoint Security 12.1 for Linux (version 12.1.0.1274)
- Kaspersky Endpoint Security 12 for Linux (version 12.0.0.6672)
- Kaspersky Endpoint Security 11.4.0 for Linux (version 11.4.0.1096)
- Kaspersky Endpoint Security 11.3.0 for Linux (version 11.3.0.7508)
- Kaspersky Endpoint Security 11.3.0 for Linux (version 11.3.0.7441)
- Kaspersky Endpoint Security 11.2.0 for Linux (version 11.2.0.4528)
Follow the instructions below under the privileged user account.
How to collect traces for troubleshooting Kaspersky Endpoint Security for Linux
When creating a request to Kaspersky Technical Support, you may be asked to send trace files as they contain diagnostic information. They can be required for solving issues or for analyzing the system load profile.
To collect traces for troubleshooting Kaspersky Endpoint Security for Linux:
- Delete previous traces (optional):
rm -f /var/log/kaspersky/kesl/kesl.*.log - Enable Detailed trace logging:
- Via kesl-control:
kesl-control --set-app-settings TraceLevel=Detailed- Via the appSettings.xml configuration file if kesl-control is not available:
- Open /var/opt/kaspersky/kesl/private/storage/appSettings.xml in a text editor (for example, vi, nano or gedit).
- Set the Detailed value for the TraceLevel parameter: <TraceLevel>Detailed</TraceLevel>
- Reproduce the issue.
- Take a screenshot or save the console output with an error where the current system time is visible.
To display timestamps in the console, you can use the following command:
date - Disable detailed trace logging:
- Via kesl-control:
kesl-control --set-app-settings TraceLevel=None- Via the appSettings.xml configuration file if kesl-control is not available:
- Open /var/opt/kaspersky/kesl/private/storage/appSettings.xml in a text editor (for example, vi, nano or gedit).
- Set the None value for the TraceLevel parameter: <TraceLevel>None</TraceLevel>
- Collect traces and other diagnostic information using the collect.sh script.
The report can be found in the /tmp/*-collect.tar.gz directory.
How to collect traces for Network Agent
Enable trace logging:
- Use level 4 by default and run the commands one by one:
mkdir -p /etc/opt/kaspersky/klnagent/1103/1.0.0.0/Debug
echo -n 4 > /etc/opt/kaspersky/klnagent/1103/1.0.0.0/Debug/TraceLevel
echo -n /opt/kaspersky/klnagent64/sbin > /etc/opt/kaspersky/klnagent/1103/1.0.0.0/Debug/TraceDir
systemctl restart klnagent64- If a Technical Support specialist requests traces of level 5, run the commands one by one:
mkdir -p /etc/opt/kaspersky/klnagent/1103/1.0.0.0/Debug
echo -n 5 > /etc/opt/kaspersky/klnagent/1103/1.0.0.0/Debug/TraceLevel
echo -n /opt/kaspersky/klnagent64/sbin > /etc/opt/kaspersky/klnagent/1103/1.0.0.0/Debug/TraceDir
systemctl restart klnagent64For Network Agent version 14 and above, you can enable trace file rotation. For example:
echo -n 500 > /etc/opt/kaspersky/klnagent/1103/1.0.0.0/Debug/TraceMaxSizeMB
Disable trace logging:
rm -rf /etc/opt/kaspersky/klnagent/1103/1.0.0.0/Debug
systemctl restart klnagent64- Collect traces and other diagnostic information using the collect.sh script.
The report can be found in the /tmp/*-collect.tar.gz directory.