Error code: x102

Internal designation: EC_BAD_CONFIG

Description: One or more Dr.Web for UNIX components cannot operate because of incorrect configuration settings.

To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.

Resolving the error

1.If you do not know the name of the component which causes the error, try to determine it by reviewing the log file.

2.If the error is produced by the SpIDer Guard component, the mode which is selected for the component operation is not probably supported by the OS. Check the selected mode and change it, if necessary. You can do it by setting the value AUTO (the Mode parameter in the [LinuxSpider] section of the configuration file).

To view and change the mode, go to the SpIDer Guard page of the web interface (if it is installed).

You also can use the commands of the command-line management tool.

To set the value to AUTO, execute the command:

# drweb-ctl cfset LinuxSpider.Mode AUTO

To restore the parameter value to the default, execute the command:

# drweb-ctl cfset LinuxSpider.Mode -r

If the error persists, build and install the loadable kernel module for SpIDer Guard manually (see the Administrator Manual).

Full version of Administrator Manual for Dr.Web for UNIX is available:

At Doctor Web official website https://download.drweb.com/doc/ (Internet connection is required).

You can view a PDF file in the <opt_dir>/share/doc directory (the suffix in the name indicates the language).

Note that operation of SpIDer Guard and of the loadable kernel module is guaranteed only on the tested UNIX distributions (see section “System Requirements and Compatibility” in Administrator Manual).

3.If this error is сaused by Dr.Web Firewall for Linux, a conflict with another firewall is probably occurring. For example, it is known that Dr.Web Firewall for Linux conflicts with FirewallD in Fedora, CentOS, Red Hat Enterprise Linux (on every launch, FirewallD corrupts traffic routing rules indicated by Dr.Web Firewall for Linux).

To resolve this error, restart Dr.Web for UNIX by executing the command:

# service drweb-configd restart

or

# drweb-ctl reload

Note that if you allow FirewallD to operate, the noted Dr.Web Firewall for Linux error can repeatedly occur on every restart of FirewallD, including a restart of an OS. You can resolve this error by disabling FirewallD (refer to the manual of FirewallD included in the manual of your OS).

4.If the error is produced by another component, restore component settings to the defaults by any of the following methods:

on the page with the component settings on the web interface (if it is installed);

use the drweb-ctl cfshow and drweb-ctl cfset commands;

edit the configuration file manually (delete all parameters from the component section).

5.If the previous steps did not help, restore Dr.Web for UNIX settings to the defaults.

To do it, clear the contents of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by executing the following commands:

# cp /etc/opt/drweb.com/drweb.ini /etc/opt/drweb.com/drweb.ini.save
# echo "" > /etc/opt/drweb.com/drweb.ini

Restart Dr.Web for UNIX after clearing the contents of the configuration file by executing the command:

# service drweb-configd restart