Dr.Web Server Log

Dr.Web Server logs the events connected with its operation.

By default, the log file name is drwcsd.log and it is located:

•On UNIX OS:

▫Linux OS: /var/opt/drwcs/log/drwcsd.log;

▫FreeBSD OS: /var/drwcs/log/drwcsd.log.

•On Windows OS: in the var subfolder of the Dr.Web Server installation folder.

The file has the plain text format (see the Appendices document, the Appendix K. Log Files Format section).

To view the Dr.Web Server log via the Control Center

1.Select the Administration item in the Control Center main menu.

2.In the opened window, select the Dr.Web Server log item of the control menu.

3.A window with a list of the Dr.Web Server logs will open. Based on the rotation mode settings, the following naming format is used for the Dr.Web Server log files: <file_name>.<N>.log or <file_name>.<N>.log.gz, where <N>—sequence number: 1, 2, etc. Therefore, if a log file name is drwcsd, the list of log files is the following:

•drwcsd.log—current log file,

•drwcsd.1.log—previous log file,

•drwcsd.2.log and so on—the greater the number, the older the version of the log.

4.To manage the log files, set the flag next to a necessary file or files. To select all log files, set the flag in the table header. As a result, the following buttons will become available on the toolbar:

Export selected log files—save a local copy of the selected log files. It can be useful, for example, to view the log file content from a remote computer.

Delete selected log files—delete the selected log files, without possibility to restore.

Managing the Dr.Web Server log level of detail

Depending on specified settings, the Dr.Web Server log is filled with different level of detail. Enabling a more detailed logging for a specific message source or for all sources can be useful for debugging and troubleshooting and can also be necessary when contacting the Doctor Web technical support. There are multiple ways to configure this parameter:

•From the Administration → Dr.Web Server configuration → Log section in the Control Center. This way allows to specify the logging level of detail for all possible sources.

•Using the -verbosity switch when launching Dr.Web Server from the command line. This way provides more flexibility, since it allows to set up the logging level of detail for a single or several different sources. The switch format is described in the Appendices document, in the H3.8. The Description of Switches section.

•From a separate configuration file named logging.conf. To do that, create a file with this name in the etc subfolder inside the Dr.Web Server installation folder. Add all necessary message sources and their desired levels of detail in the following format: <message_source>:<level>. The levels of detail specified for message sources in the logging.conf override any levels configured for the same sources in any other way.

Example of the logging.conf content:

Besides the comma, you can also use any whitespace characters, like a normal space, tab, newline, etc. as the separators. You can check the list of available message sources in the Dr.Web Server log file directly or by running the following command in the Administration → Lua console section of the Control Center: drwcs.log_subsystems(). All possible levels of detail are listed in the Appendices document, in Appendix K. Log Files Format.

•For Dr.Web Servers running a UNIX system-based OS, you can use a designated switch in the configuration file named local.conf. Please see below for information about this file.

Logging Setup for UNIX

It is possible to set up the logging on Dr.Web Servers running a UNIX system-based OS via a separate configuration file:

•for Linux OS: /var/opt/drwcs/etc/local.conf;

•for FreeBSD OS: /var/drwcs/etc/local.conf.

The local.conf file content:

Parameter values correspond with the values of command line switches for the Dr.Web Server launch:

•-verbosity=<detail_level>—level of detail of the Dr.Web Server log.

•-rotate=<N><f>,<M><u>—rotation mode of the Dr.Web Server log.

The switches are described in detail in the Appendices document, the H3.8. The Description of Switches section.

During the Dr.Web Server update or removal, the local.conf file is backed up. That allows to manage the log level of detail in case of a package update of Dr.Web Server.