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 account permissions 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.
Unassisted modification of Kaspersky Security settings in the ways not described in the Kaspersky Security Help or in the recommendations from the Technical Support specialists can lead to slowdowns and malfunctions of the operating system, decrease of the virtual machine protection level, as well as to a violation of the availability and integrity of the processed information.
Expand all | Collapse all
General settings
trace_level = 0
Determines the trace level for all SVM trace files except the SnmpTool.log 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.
The trace file is used if system log usage is disabled (see section [syslog]).
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.
The trace file is used if system log usage is disabled (see section [syslog]).
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
This section contains processing and rotation settings for the Protection Server trace file (ScanServer.log).
period = 3
File rotation frequency.
Possible values: 1 – monthly, 2 – weekly, 3 – daily, 4 – hourly.
max_file_size = 1073741824
The maximum trace file size in bytes. When reached, rotation is performed.
Possible values: 0 – unlimited, 1073741824 – 1 GB.
max_file_count = 15
The maximum number of the trace files. When the limit is reached, old files are deleted.
Possible values: number or 0 – unlimited.
new_file_on_start = 1
Logging to a new file or to the last available trace file when the Protection Server starts.
Possible values: 1 – write to a new file, 0 – write to the last created file.
[extra_tracing] section
enabled = 1
Logging general information to trace files every time the trace level is changed (information about the license, KSN usage, and the anti-virus databases used). Possible values: 0 – disabled, 1 – enabled.
[syslog] section
This section contains the system log usage settings.
enabled = 0
System log usage. Possible values: 1 – enable, 0 – disable.
If the system log usage is disabled, data is logged to the Protection Server trace file. The file name is specified by the trace_file setting (see the General settings section).
program_name = ScanServer
System log name.
facility = 176
System log category (LOG_LOCAL6 = 176).
format = %I %p:
Syslog entry format: %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.
[dumps] section
This section contains the settings of the Protection Server dump files.
dir = /var/opt/kaspersky/la/dumps
Directory for logging dumps.
schema = ScanServer_%d_%p_%n.dmp
Name configuration:
- %d – date and time (08.27_19.39);
- %p – process ID;
- %n – dump number in the session.
max = 10
The maximum number of dumps in the repository.
freeMiB = 1024
The minimum amount of free disk space required to write the dump (in MB).