Error code: x109

Description: A program component cannot be in operation because an incompatible software is detected. This software interrupts correct component operation.

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 this error is produced by SpIDer Gate, most likely that there is an incompatible software in operating system. This software generates rules for the NetFilter system firewall, which prevents SpIDer Gate from correct operation. Probably, you have Shorewall or SuseFirewall2 installed in the system (in SUSE Linux OS). The application that configure the NetFilter system firewall sometimes check the integrity of the specified rule system and rewrite it. This is the main reason of SpIDer Gate conflict with such applications.

Reconfigure incompatible software so as it does not interfere in SpIDer Gate operation. If it is not possible, disable the software so as it does not load at the operating system startup any more. You can try to configure the SuseFirewall2 application (in SUSE Linux OS), following the steps:

1)Open the configuration file of SuseFirewall2 (by default, this is the /etc/sysconfig/SuSEfirewall2 file).

2)Find the following text block:

# Type: yesno
#
# Install NOTRACK target for interface lo in the raw table. Doing so
# speeds up packet processing on the loopback interface. This breaks
# certain firewall setups that need to e.g. redirect outgoing
# packets via custom rules on the local machine.
#
# Defaults to "yes" if not set
#
FW_LO_NOTRACK=""

3)Set the parameter value to “no”:

FW_LO_NOTRACK="no"

4)Restart SuseFirewall2. To do it, use the following command:

# rcSuSEfirewall2 restart

 

Note that if SuseFirewall2 does not have the FW_LO_NOTRACK option in its settings, to resolve the conflict, disable the application so that it does not load at the system startups any more (for example, it is necessary for OS SUSE Linux Enterprise Server 11).

After reconfiguring or disabling the conflict application, restart SpIDer Gate.

2.If the error is produced by another component, disable or reconfigure the incompatible software so as to prevent any interference with the Dr.Web for UNIX operation.