settracelevel

This command lets you configure the trace level for the Protection Server (ScanServer.log).

The trace level is changed immediately if the <Immediately>=yes parameter is set. Otherwise, the change occurs after a restart of the SVM or Protection Server (the manageservices restart scanserver command).

Settings

<TraceLevel> [<Immediately>]

where:

• <TraceLevel> is a numerical value that determines the trace level. Possible values:
  • 0: creation of trace files is disabled.
  • 100: informational messages about the Protection Server components being started and stopped.
  • 200: messages about critical errors in the Protection Server operation.
  • 300: messages about errors and critical errors in the Protection Server operation.
  • 400: critical warnings and messages about ordinary and critical errors.
  • 500: all warnings and messages about ordinary and critical errors.
  • 600: important messages, all warnings and messages about ordinary and critical errors.
  • 700: informational messages, important messages and all warnings and messages about ordinary and critical errors.
  • 800: debugging messages and all informational and important messages, as well as all warnings and messages about ordinary and critical errors.
  • 900: debugging messages with more detailed information and all informational and important messages, as well as all warnings and messages about ordinary and critical errors.
  • 1000: all possible messages and warnings.
• <Immediately> = yes|no is an indicator determining when the new trace level settings should be applied (optional parameter). Possible values:
  • yes: apply immediately.
  • no: apply after restart of the SVM or the scanserver service (the manageservices restart scanserver command).

Specific errors

0150 Could not update <configfile>. Failed to update the configuration file /etc/opt/kaspersky/la/ScanServer.conf. Make sure that the file exists and is accessible.