Error code: x102

Description: One of the program components cannot be in operation because of incorrect configuration settings.

For details on the place and the reason of the error, refer to the program log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS).

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, most likely that the mode which is selected for the component operation is not supported by 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 may 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, manually build and install the loadable kernel module for SpIDer Guard (see the Appendix G in Administrator Manual).

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

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

At Doctor Web official website http://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).

3.If the error is produced by the Dr.Web Firewall for Linux component, most likely that the component conflicts with another firewall. It is known that Dr.Web Firewall for Linux conflicts with FirewallD in Fedora, CentOS, and Red Hat Enterprise Linux OSes (at each restart, FirewallD breaks traffic routing rules that are defined by Dr.Web Firewall for Linux). To resolve the error, restart the product by executing the command

# service drweb-configd restart

or

# drweb-ctl reload

 

Please note that if you will not disable FirewallD, the described Dr.Web Firewall for Linux error may repeat during each FirewallD restarting, including cases, when the OS is restarted. You can resolve the conflict, if you disable FirewallD (refer to FirewallD manual, that is included into manual of the OS which is used).

 

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 do not help, restore program’s 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 the program after clearing the contents of the configuration file by executing the command

# service drweb-configd restart