Settings in the ScanServer.conf file

The ScanServer.conf file contains the SVM operation settings. The file is located on the SVM in the /etc/opt/kaspersky/la/ directory.

Root privileges are required to view and modify the file.

This section describes the settings in the ScanServer.conf file that allow you to configure logging of the SVM traces and dumps, usage of the SVM system log, and agree to the terms of the End-User License Agreement. Information about other settings, if necessary, can be obtained from the Technical Support.

Self-guided modification Kaspersky Security settings in ways not described in the application Help or in recommendations of Technical Support can slow down the operating system or cause it to malfunction, reduce the protection level of virtual machines, or cause a violation of the availability and integrity of the information being processed.

Expand all | Collapse all

General settings

trace_level = 0

Specifies the trace level for the ScanServer.log Protection Server trace file.

Possible values:

0 – creation of trace files is disabled.
100: "Always" – informational messages about Kaspersky Security components being started and stopped.
200: "Critical" – messages about critical errors that can result in termination of Kaspersky Security.
300: "Error": messages about errors, which can result in partial inoperability of Kaspersky Security.
400: "Danger" – warnings about the possibility of critical errors.
500: "Warning" – warnings about possible errors.
600: "Important" – important messages.
700: "Information" – informational messages.
800: "Debug": debug messages used by developers.
900: "Paranoiac" – debug messages with more detailed information used by developers.
1000: "Any" – all possible messages and warnings.

After changing the trace level, restart the scanserver service by running the following command:

systemctl reload la-scanserver

trace_protected_data

Writing potentially personal data (for example, passwords) to trace files.

Possible values:

0 - do not write potentially personal data to trace files (default value).
1 - write potentially personal data to trace files.

trace_file = /var/log/kaspersky/la/ScanServer.log

The name of the Protection Server trace file. The date is appended to the file name, for example, ScanServer.2020-11-19T130126.log. The rotation settings are controlled by the scanserver service.

trace_format = %Y-%m-%dT%X %I %p:

The format for logging the lines in the Protection Server trace file (ScanServer.log).

Qualifiers: %Y = year, %m = month, %d = day, %H = hour, %M = minute, %S = second, %i = millisecond, %p = trace level, %N = device name, %P = process identifier (PID), %I = thread ID, %C = component ID, %D = component instance ID, %X = time.

accept_eula_and_privacypolicy = yes|no

Accept or decline the terms of Kaspersky Security End User License Agreement between you and Kaspersky and the Privacy Policy that describes processing and transmission of data.

Possible values: yes – accept the terms of the End-User License Agreement and the Privacy Policy, no – do not accept the terms of the End-User License Agreement and the Privacy Policy.

You must accept the terms of the End User License Agreement and the Privacy Policy for the proper SVM operation.

By setting this parameter to 'yes', you confirm the following:

You have fully read, understood and accept the terms and conditions of Kaspersky Security End User License Agreement.
You have fully read and understood the Privacy Policy, you are aware and agree that your data will be handled and transmitted (including to third countries) as described in the Privacy Policy.

The text of the End User License Agreement and Privacy Policy is included in the Kaspersky Security distribution kit.

[rotation_settings] section

[extra_tracing] section

[dumps] section

Page top