Appendix D. Known Errors

•To figure out the place and the cause of the error, read the contents of the program complex log (by default, it is located in /var/log/syslog file or /var/log/messages file, depending on the OS installed).

•To identify the error, we recommend you to configure logging to a separate file and enable output of extended information to the log. For that, execute the following commands:

•To return to the default logging method and verbosity level, execute the following commands:

Error message

Error on monitor channel

Error code

Description

One of the components cannot connect with the configuration daemon Dr.Web ConfigD.

Resolving the error:

1.Restart the configuration daemon by executing the command

# service drweb-configd restart

2.Check whether the authentication mechanism for PAM is installed, configured and operates correctly. If not so, install and configure it (for details refer to administration guides and manuals for your OS distribution).

3.If PAM is configured correctly and restart of the configuration daemon does not help, restore program 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 configuration daemon after clearing the contents of the configuration file.

4.If it is not possible to start the configuration daemon, reinstall the drweb-configd package.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message	Operation is in pending state
Error code	x3
Description	An operation requested by the user is in pending state (possibly, a network connection is currently establishing or one of the program components is loading or initializing, which takes a long time).
Resolving the error: 1.Wait for the operation to start. If necessary, repeat the required action after some time.
If the error persists, contact technical support and be ready to name the error code.

Error message	IPC connection terminated
Error code	x6
Description	An interprocess communication (IPC) connection with one of the components is terminated (most likely, the component shuts down because of the user command or being idle).
Resolving the error: 1.If the operation is not finished, start it again. Otherwise, the termination is not an error.
If the error persists, contact technical support and be ready to name the error code.

Error message	The component is not installed.
Error code	x10
Description	Some function of Dr.Web for Linux is not available because the corresponding component (performing this function) is not installed in the system.
Resolving the error: 1.Install or reinstall the package with the necessary component: •drweb-filecheck, if Scanner is not installed •drweb-spider, if SpIDer Guard is not installed •drweb-gated, if SpIDer Guard is not installed •drweb-update, if Updater is not installed 2.If the error persists, or you cannot detect which component is not installed, uninstall Dr.Web for Linux and then install it again on the system. For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.
If the error persists, contact technical support and be ready to name the error code.

Error message

Subsystem state is unknown

Error code

x13

Description

It was discovered that the current state is not known for a certain subsystem that is part of this software and is needed for carrying out the requested operation.

Resolving the error:

1.Repeat the operation.

2.If the error persists, restart the program by executing the command

# service drweb-configd restart

and then repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message	Not enough memory
Error code	x21
Description	Not enough memory to complete the required operation (for example, an attempt to open a large file).
Resolving the error: 1.Increase size of available memory for program processes (for example, by changing the limits with the ulimit command), restart the program and repeat the operation.
If the error persists, contact technical support and be ready to name the error code.

Error message	IO error
Error code	x22
Description	An input/output (I/O) error occurs (for example, the drive is not initialized yet or the partition of the file system is not available anymore).
Resolving the error: 1.Check whether the required I/O device or the partition of the file system is available. If necessary, mount it and repeat the operation.
If the error persists, contact technical support and be ready to name the error code.

Error message	Permission denied
Error code	x24
Description	There are not enough permissions to access the specified object of the file system (file or directory).
Resolving the error: 1.Check whether the path is correct and whether the component has required permissions. If it is necessary to access the object, change access permissions or elevate component’s permissions. Repeat the operation.
If the error persists, contact technical support and be ready to name the error code.

Error message

Data file corrupted

Error code

x26

Description

Requested data is corrupted.

Resolving the error:

1.Repeat the operation.

2.If the error persists, restart the program by executing the command

# service drweb-configd restart

and then repeat the operation.

If the error persists, contact technical support and be ready to name the error code.

Error message	Read-only file system
Error code	x28
Description	On attempt to create or change an object of the file system (directory, file or socket), it is detected that the file system is read-only.
Resolving the error: 1.Check the path. Change it so that the path indicates the writable partition of the file system and repeat the operation.
If the error persists, contact technical support and be ready to name the error code.

Error message	Network error
Error code	x29
Description	A network error occurs (possibly, a remote node stops responding unexpectedly or the required connection fails).
Resolving the error: 1.Check whether the network is available and network settings are correct. If necessary, change network settings and repeat the operation.
If the error persists, contact technical support and be ready to name the error code.

Error message	Not a regular file
Error code	x33
Description	During accessing an object of the file system. it is detected that it is not a regular file (that is, it is a directory, socket or other object of the file system).
Resolving the error: 1.Check the name of the file. If necessary, change the path so that it indicates the regular file and repeat the operation.
If the error persists, contact technical support and be ready to name the error code.

Error message

Virus database corrupted

Error code

x40

Description

Virus databases are corrupted.

Resolving the error:

1.Check the path to the virus database directory. Change the path, if necessary (the VirusBaseDir parameter in the [Root] section of the configuration file).

To view and correct the path, use the commands of the command-line management tool:

•To view current parameter value, execute the following command:

$ drweb-ctl cfshow Root.VirusBaseDir

•To set a new parameter value, execute the command

# drweb-ctl cfset Root.VirusBaseDir <new path>

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

# drweb-ctl cfset Root.VirusBaseDir -r

2.Update virus databases in one of the following ways:

•Click Update on the update control page of the main window of the application.

•Click Update in the context menu of the status indicator in the notification area.

•Execute the command:

$ drweb-ctl update

If the error persists, contact technical support and be ready to name the error code.

Error message

Non-supported virus database version

Error code

x41

Description

Current virus databases are meant for earlier program version.

Resolving the error:

1.Check the path to the virus database directory. Change the path, if necessary (the VirusBaseDir parameter in the [Root] section of the configuration file).

To view and correct the path, use the commands of the command-line management tool:

•To view current parameter value, execute the following command:

$ drweb-ctl cfshow Root.VirusBaseDir

•To set a new parameter value, execute the command

# drweb-ctl cfset Root.VirusBaseDir <new path>

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

# drweb-ctl cfset Root.VirusBaseDir -r

2.Update virus databases in one of the following ways:

•Click Update on the update control page of the main window of the application.

•Click Update in the context menu of the status indicator in the notification area.

•Execute the command:

$ drweb-ctl update

If the error persists, contact technical support and be ready to name the error code.

Error message

Empty virus database

Error code

x42

Description

Virus databases are empty.

Resolving the error:

1.Check the path to the virus database directory. Change the path, if necessary (the VirusBaseDir parameter in the [Root] section of the configuration file).

To view and correct the path, use the commands of the command-line management tool:

•To view current parameter value, execute the following command:

$ drweb-ctl cfshow Root.VirusBaseDir

•To set a new parameter value, execute the command

# drweb-ctl cfset Root.VirusBaseDir <new path>

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

# drweb-ctl cfset Root.VirusBaseDir -r

2.Update virus databases in one of the following ways:

•Click Update on the update control page of the main window of the application.

•Click Update in the context menu of the status indicator in the notification area.

•Execute the command:

$ drweb-ctl update

If the error persists, contact technical support and be ready to name the error code.

Error message

Non-supported virus database combination

Error code

x44

Description

The current virus database combination cannot be supported.

Resolving the error:

1.Check the path to the virus database directory. Change the path, if necessary (the VirusBaseDir parameter in the [Root] section of the configuration file).

To view and correct the path, use the commands of the command-line management tool:

•To view current parameter value, execute the following command:

$ drweb-ctl cfshow Root.VirusBaseDir

•To set a new parameter value, execute the command

# drweb-ctl cfset Root.VirusBaseDir <new path>

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

# drweb-ctl cfset Root.VirusBaseDir -r

2.Update virus databases in one of the following ways:

•Click Update on the update control page of the main window of the application.

•Click Update in the context menu of the status indicator in the notification area.

•Execute the command:

$ drweb-ctl update

If the error persists, contact technical support and be ready to name the error code.

Error message	Scan limit reached
Error code	x45
Description	When scanning an object, the specified limits have been reached (for example, the limit on the size of an unpacked file, on the nesting depth and others).
Resolving the error: 1.Change limits for scanning (in the component settings) by any of the following methods: •On the page with the component settings in the application settings window. •Use the drweb-ctl cfshow and drweb-ctl cfset commands. 2.After changing the settings, repeat the previously attempted operation.
If the error persists, contact technical support and be ready to name the error code.

Error message	Access token is invalid
Error code	x49
Description	One of the program components provides invalid authorization token on attempt to access the operation, requiring elevated privileges.
Resolving the error: 1.Enter valid credentials of the user with the necessary privileges. Try to complete authentication again.
If the error persists, contact technical support and be ready to name the error code.

Error message

Not allowed in central protection mode

Error code

x63

Description

The required action can be performed only if the program operates in Standalone mode.

Resolving the error:

1.Change product’s operation mode to Standalone mode and repeat the operation.

2.To change the mode

•Clear the Enable the central protection mode check box on the Mode settings page.

•Or execute the command

# drweb-ctl esdisconnect

If the error persists, contact technical support and be ready to name the error code.

Error message

Feature not implemented

Error code

x65

Description

Required features of one of the components are not implemented in the current version of the program.

Resolving the error:

1.Restore software defaults by clearing the contents of the configuration file /etc/opt/drweb.com/drweb.ini. It is recommended to back up the file before the procedure. For example:

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

2.Restart the program after clearing the contents of the configuration file by executing the command

# service drweb-configd restart

If the error persists, contact technical support and be ready to name the error code.

Error message

Unknown option

Error code

x66

Description

The configuration file contains parameters unknown or non-supported in the current version of the program.

Resolving the error:

1.Open the /etc/opt/drweb.com/drweb.ini file in any text editor, remove the line, containing invalid parameter. Save the file and restart the program by executing the command:

# service drweb-configd restart

2.If it does not help, restore program’s settings to the defaults.

To do this, clear the contents of the file /etc/opt/drweb.com/drweb.ini (it is recommended to back up 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.

If the error persists, contact technical support and be ready to name the error code.

Error message

Unknown section

Error code

x67

Description

The configuration file contains sections unknown or non-supported in the current version of the program.

Resolving the error:

1.Open the /etc/opt/drweb.com/drweb.ini file in any text editor, remove the unknown section. Save the file and restart the program by executing the command:

# service drweb-configd restart

2.If it does not help, restore program’s settings to the defaults.

To do this, clear the contents of the file /etc/opt/drweb.com/drweb.ini (it is recommended to back up 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.

If the error persists, contact technical support and be ready to name the error code.

Error message

Invalid option value

Error code

x68

Description

One of the parameters in the configuration file contains invalid value for the parameter.

Resolving the error:

1.Set the valid parameter value by any of the following methods:

•On the page with the component settings in the application settings window.

•Use the drweb-ctl cfshow and drweb-ctl cfset commands.

If you do not know which value is valid for the parameter, refer to the help file of the component which uses this parameter. You may also restore parameter value to the default.

2.You may also directly edit the configuration file /etc/opt/drweb.com/drweb.ini. To do this, open the configuration file in any text editor, find the line containing invalid parameter value, set valid value, then save the file and restart the program by executing the command:

# service drweb-configd restart

3.If the previous steps do not help, restore program’s settings to the defaults.

To do this, clear the contents of the file /etc/opt/drweb.com/drweb.ini (it is recommended to back up 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.

If the error persists, contact technical support and be ready to name the error code.

Error message

Invalid state

Error code

x69

Description

The program or one of the components is in invalid state to complete the required operation.

Resolving the error:

1.Repeat the required action after some time.

2.If the error persists, restart the program by executing the command

# service drweb-configd restart

If the error persists, contact technical support and be ready to name the error code.

Error message

Only one value allowed

Error code

x70

Description

One of the parameters in the configuration file contains a list of values; while it is allowed to contain only a single value.

Resolving the error:

1.Set the valid parameter value by any of the following methods:

•On the page with the component settings in the application settings window.

•Use the drweb-ctl cfshow and drweb-ctl cfset commands.

If you do not know which value is valid for the parameter, refer to the help file of the component which uses this parameter. You may also restore parameter value to the default.

# service drweb-configd restart

3.If the previous steps do not help, restore program’s settings to the defaults.

To do this, clear the contents of the file /etc/opt/drweb.com/drweb.ini (it is recommended to back up 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.

If the error persists, contact technical support and be ready to name the error code.

Error message

Tag value is invalid

Error code

x71

Description

One of the sections in the configuration file with a name containing a unique tag identifier has an invalid tag identifier.

Resolving the error:

1.If the error occurs on attempt to usde the command

# drweb-ctl cfset <section>.<parameter> <new value>

set valid value for the tag and save the section again.

2.If the section is saved directly in the configuration file /etc/opt/drweb.com/drweb.ini, edit the file. To do this, open the configuration file in any text editor, find the section name containing invalid tag value and set valid value for the tag. Save the file and restart the program by executing the command:

# service drweb-configd restart

3.If the previous steps do not help, restore program’s settings to the defaults.

To do this, clear the contents of the file /etc/opt/drweb.com/drweb.ini (it is recommended to back up 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.

If the error persists, contact technical support and be ready to name the error code.

Error message

Cannot backup before update.

Error code

x89

Description

Prior to downloading the updates from the updates server, an attempt to make a backup copy of the files to be updated failed.

Resolving the error:

1.Check the path to the directory that stores backup copies of the files that are updated. Change the path, if necessary (the BackupDir parameter in the [Update] section of the configuration file).

In order to view and correct the path, you may use the commands of the command line management tool.

•To view current parameter value, execute the following command:

$ drweb-ctl cfshow Update.BackupDir

•To set a new parameter value, execute the command

# drweb-ctl cfset Update.BackupDir <new path>

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

# drweb-ctl cfset Update.BackupDir -r

2.Update virus databases in one of the following ways:

•Click Update on the update control page of the main window of the application.

•Click Update in the context menu of the status indicator in the notification area.

•Execute the command:

$ drweb-ctl update

3.If the error persists, check whether the user under whose account the Update component is running has a write permission to the directory specified in the BackupDir. The name of this user is specified in the RunAsUser parameter. If necessary, change the user name specified in the RunAsUser parameter or grant the missing permissions in the directory’s properties.

4.If the error persists, reinstall the drweb-update package.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

Invalid DRL file

Error code

x90

Description

An integrity violation of one of the files with the list of update servers is detected.

Resolving the error:

1.Check the path to the file with the list of servers. Change the path, if necessary (parameters with *DrlPath in [Update] section of the config file. To do this, use commands of the command line management tool.

•To view current parameter value, execute the command (<*DrlPath> should be changed for a name of the parameter. If you do not know the parameter name, review values of all parameters in the section omitting the part specified in square brackets):

$ drweb-ctl cfshow Update[.<*DrlPath>]

•To set new parameter value, execute the command (<*DrlPath> should be changed for a name of the parameter):

# drweb-ctl cfset Update.<*DrlPath> <new path>

•To restore parameter value to the default, execute the command (<*DrlPath> should be changed for a name of the parameter)

# drweb-ctl cfset Update.<*DrlPath> -r

2.Update virus databases in one of the following ways:

•Click Update on the update control page of the main window of the application.

•Click Update in the context menu of the status indicator in the notification area.

•Execute the command:

$ drweb-ctl update

3.If the error persists, install drweb-bases and drweb-dws components (packages) separately and then start an update.

4.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

Invalid LST file

Error code

x91

Description

An integrity violation of the file containing the list of updated virus databases is detected.

Resolving the error:

1.Update virus databases in one of the following ways:

•Click Update on the update control page of the main window of the application.

•Click Update in the context menu of the status indicator in the notification area.

•Execute the command:

$ drweb-ctl update

2.If the error persists, reinstall the drweb-update package.

3.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

Invalid compressed file

Error code

x92

Description

An integrity violation of the downloaded file containing updates is detected.

Resolving the error:

1.Update virus databases in one of the following ways:

•Click Update on the update control page of the main window of the application.

•Click Update in the context menu of the status indicator in the notification area.

•Execute the command:

$ drweb-ctl update

If the error persists, contact technical support and be ready to name the error code.

Error message

Proxy authentication error

Error code

x93

Description

The program fails to connect to update servers using the proxy server specified in the settings.

Resolving the error:

1.Check the parameters used to connect to a proxy server (they are set in the Proxy parameter in the [Update] section of the configuration file). If necessary, change the proxy server or do not use proxy for connections.

To view and set the connection parameters, go to the main settings page.

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

•To view current parameter value, execute the following command:

$ drweb-ctl cfshow Update.Proxy

•To set a new parameter value, execute the command

# drweb-ctl cfset Update.Proxy <new parameters>

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

# drweb-ctl cfset Update.Proxy -r

2.Update virus databases in one of the following ways:

•Click Update on the update control page of the main window of the application.

•Click Update in the context menu of the status indicator in the notification area.

•Execute the command:

$ drweb-ctl update

If the error persists, contact technical support and be ready to name the error code.

Error message

No update servers available

Error code

x94

Description

The program fails to connect to any of the update servers.

Resolving the error:

1.Check whether the network is available. Change network settings, if necessary.

2.If the network access is available only via a proxy server, specify the parameters of connection to the proxy server (they are set in the Proxy parameter in the [Update] section of the configuration file). If necessary, change the proxy server or do not use proxy for connections.

To view and set the connection parameters, go to the main settings page.

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

•To view current parameter value, execute the following command:

$ drweb-ctl cfshow Update.Proxy

•To set a new parameter value, execute the command

# drweb-ctl cfset Update.Proxy <new parameters>

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

# drweb-ctl cfset Update.Proxy -r

3.If the network connection settings (including the proxy server ones) are correct, but the error occurs, make sure you are using an available list of update servers. The list of update servers used is indicated in the view parameters*DrlPath in[Update] section of the configuration file. Note that if the parameters *CustomDrlPath indicate on the existing correct file of the server list, the servers specified there will be used instead of the servers of the standard update zone (the value specified in the corresponding *DrlPath parameter, is ignored).

In order to view and configure connection settings, you may use the commands of the command line management tool.

To view current parameter value, execute the command (<*DrlPath> should be changed for a name of the parameter. If you do not know the parameter name, review values of all parameters in the section omitting the part specified in square brackets):

$ <%CTL_MODULE%> cfshow Update[.<*DrlPath>]

To set new parameter value, execute the command (<*DrlPath> should be changed for a name of the parameter):

# <%CTL_MODULE%> cfset <%UPDATE_SECTION%>.<*DrlPath> <new path>

To restore parameter value to the default, execute the command (<*DrlPath> should be changed for a name of the parameter)

# <%CTL_MODULE%> cfset <%UPDATE_SECTION%>.<*DrlPath> -r

4.Update virus databases in one of the following ways:

•Click Update on the update control page of the main window of the application.

•Click Update in the context menu of the status indicator in the notification area.

•Execute the command:

$ drweb-ctl update

If the error persists, contact technical support and be ready to name the error code.

Error message

Invalid key file format

Error code

x95

Description

The key file format is violated.

Resolving the error:

1.Check whether you have the key file and the path to it. You can specify the path to the key file in the KeyPath parameter in the [Root] section of the configuration file.

To view the license parameters and set the path to the key file, go to the License Manager page of the main page of the application.

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

•To view current parameter value, execute the following command:

$ drweb-ctl cfshow Root.KeyPath

•To set a new parameter value, execute the command

# drweb-ctl cfset Root.KeyPath <path to file>

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

# drweb-ctl cfset Root.KeyPath -r

2.If you do not have the key file or the used key file is corrupted, purchase and install it. For more details on the key file, purchase and installation refer to the Licensing section.

3.To install the key file, you may use the License Manager.

4.You can also view current license options in user’s webpage My Dr.Web at https://support.drweb.com/get+cabinet+link/.

If the error persists, contact technical support and be ready to name the error code.

Error message	License is expired
Error code	x96
Description	The used license is expired.
Resolving the error: 1.Purchase a new license and install a key file that you will receive. For more details on ways to purchase the license and installation of the key file refer to the Licensing section. 2.To install the purchased key file, you may use the License Manager. 3.You can also view current license options in user’s webpage My Dr.Web at https://support.drweb.com/get+cabinet+link/.
If the error persists, contact technical support and be ready to name the error code.

Error message	Network operation timed out.
Error code	x97
Description
Resolving the error: 1.Check whether the network is available and network settings are correct. If necessary, change network settings and repeat the operation. 2.If an error persists during the update, additionally check parameters of the proxy server usage, and if necessary, change the used proxy server or do not use it at all.
If the error persists, contact technical support and be ready to name the error code.

Error message

Invalid checksum

Error code

x98

Description

A checksum of the downloaded file containing updates is detected.

Resolving the error:

1.Restart the update after some time in one of the following ways:

•Click Update on the update control page of the main window of the application.

•Click Update in the context menu of the status indicator in the notification area.

•Execute the command:

$ drweb-ctl update

If the error persists, contact technical support and be ready to name the error code.

Error message	Invalid demo key file
Error code	x99
Description	The used demo key file is invalid (for example, it was received from another computer).
Resolving the error: 1.Send a request for a new demo period for this computer or purchase a new license and install a key file that you will receive. For more details on ways to purchase the license and installation of the key file refer to the Licensing section. 2.To install the purchased key file, you may use the License Manager. 3.You can also view current license options in user’s webpage My Dr.Web at https://support.drweb.com/get+cabinet+link/.
If the error persists, contact technical support and be ready to name the error code.

Error message	Key file is blocked
Error code	x100
Description	The used license is blocked (probably, the license agreement conditions on using the Dr.Web program are broken).
Resolving the error: 1.Purchase a new license and install a key file that you will receive. For more details on ways to purchase the license and installation of the key file refer to the Licensing section. 2.To install the purchased key file, you may use the License Manager. 3.You can also view current license options in user’s webpage My Dr.Web at https://support.drweb.com/get+cabinet+link/.
If the error persists, contact technical support and be ready to name the error code.

Error message	Invalid license
Error code	x101
Description	The used license is meant for other product or does not allow operation of the installed product components.
Resolving the error: 1.Purchase a new license and install a key file that you will receive. For more details on ways to purchase the license and installation of the key file refer to the Licensing section. 2.To install the purchased key file, you may use the License Manager. 3.You can also view current license options in user’s webpage My Dr.Web at https://support.drweb.com/get+cabinet+link/.
If the error persists, contact technical support and be ready to name the error code.

Error message

Invalid configuration

Error code

x102

Description

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

Resolving the error:

1.If you do not know the name of the component which causes the error, try to determine it 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).

In order to view and correct the mode, you 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

Note that operation of SpIDer Guard and of the loadable kernel module is guaranteed only on the tested Linux distributives (see System Requirements).

3.If this error is produced by SpIDer Gate, most likely that there is a conflict with another firewall. For example, it is known that SpIDer Gate conflicts with FirewallD in Fedora, CentOS, Red Hat Enterprise Linux (on every launch, FirewallD corrupts traffic routing rules indicated by SpIDer Gate). To resolve this error, restart the program by executing the command

# service drweb-configd restart

# drweb-ctl reload

Note that if you allow FirewallD to operate, the noted SpIDer Gate 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 the component settings to the defaults by any of the following methods:

•Use the drweb-ctl cfshow and drweb-ctl cfset commands.

•Edit the configuration file manually by deleting all parameters from the component section.

5.If the previous steps do not help, restore program’s settings to the defaults.

To do this, clear the contents of the file /etc/opt/drweb.com/drweb.ini (it is recommended to back up 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

If the error persists, contact technical support and be ready to name the error code.

Error message

Invalid executable file

Error code

x104

Description

One of the program components cannot run due to incorrect path or corrupted execution file contents.

Resolving the error:

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

2.Check the path to the executable file of the component in the program configuration file (the ExePath parameter in the component section), by executing the following command (change <component section> for the name of the corresponding section of the configuration file):

$ drweb-ctl cfshow <component section>.ExePath

3.Restore the path to the default by executing the following command (change <component section> for the name of the corresponding section of the configuration file):

# drweb-ctl cfset <component section>.ExePath -r

4.If the previous steps do not help, reinstall the package of the corresponding component.

•drweb-filecheck, if the executable file of Scanner is corrupted

•drweb-spider, if the executable file of SpIDer Gate is corrupted.

•drweb-gated, if the executable file of SpIDer Gate is corrupted

•drweb-update, if the executable file of Updater is corrupted

5.If the error persists, or you cannot detect which executable file is invalid, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

Virus-Finding Engine is not available

Error code

x105

Description

The file of anti-virus engine Dr.Web Virus-Finding Engine is missing or unavailable (it is necessary for threat detection).

Resolving the error:

1.Check the path to the drweb32.dll anti-virus engine file. Change the path, if necessary (the CoreEnginePath parameter in the [Root] section of the configuration file).

In order to view and correct the path, you may use the commands of the command line management tool.

•To view current parameter value, execute the command

$ drweb-ctl cfshow Root.CoreEnginePath

•To set a new parameter value, execute the command

# drweb-ctl cfset Root.CoreEnginePath <new path>

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

# drweb-ctl cfset Root.CoreEnginePath -r

2.Update virus databases in one of the following ways:

•Click Update on the update control page of the main window of the application.

•Click Update in the context menu of the status indicator in the notification area.

•Execute the command:

$ drweb-ctl update

3.If the path is correct and the error persists after updating virus databases, reinstall the drweb-bases package.

4.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

No virus databases

Error code

x106

Description

Virus databases are not found.

Resolving the error:

1.Check the path to the virus database directory. Change the path, if necessary (the VirusBaseDir parameter in the [Root] section of the configuration file).

In order to view and correct the path, you may use the commands of the command line management tool.

•To view current parameter value, execute the command

$ drweb-ctl cfshow Root.VirusBaseDir

•To set a new parameter value, execute the command

# drweb-ctl cfset Root.VirusBaseDir <new path>

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

# drweb-ctl cfset Root.VirusBaseDir -r

2.Update virus databases in one of the following ways:

•Click Update on the update control page of the main window of the application.

•Click Update in the context menu of the status indicator in the notification area.

•Execute the command:

$ drweb-ctl update

3.If the error persists, install the drweb-bases package containing virus databases and anti-virus engine executable file.

4.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

Process terminated by signal

Error code

x107

Description

A component shuts down (possibly, because of the user command or being idle).

Resolving the error:

1.If the operation is not finished, start it again. Otherwise, the shutdown is not an error.

2.If a component shuts down constantly, restore its settings to the defaults by any of the following methods:

•Use the drweb-ctl cfshow and drweb-ctl cfset commands.

•Edit the configuration file manually (by deleting all parameters from the component section).

3.If it does not help, restore program’s settings to the defaults.

To do this, clear the contents of the file /etc/opt/drweb.com/drweb.ini (it is recommended to back up 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

If the error persists, contact technical support and be ready to name the error code.

Error message

Unexpected process termination

Error code

x108

Description

A component unexpectedly shuts down because of a failure.

Resolving the error:

1.Repeat the terminated operation.

2.If the component constantly shuts down abnormally, restore its settings to the defaults by any of the following methods:

•Use the drweb-ctl cfshow and drweb-ctl cfset commands.

•Edit the configuration file manually (by deleting all parameters from the component section).

3.If it does not help, restore program’s settings to the defaults.

To do this, clear the contents of the file /etc/opt/drweb.com/drweb.ini (it is recommended to back up 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

4.If the error persists after restoring program settings, reinstall the component package.

5.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

Incompatible software detected

Error code

x109

Description

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

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 by executing 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).

5)After reconfiguring or disabling the conflict application, restart SpIDer Gate (disable it and enable again on the relevant page):

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 Linux operation.

If the error persists, contact technical support and be ready to name the error code.

Error message

Invalid VadeRetro library

Error code

x110

Description

A file of VadeRetro anti-spam library is missing, unavailable or corrupted (it is necessary for email scanning)

Resolving the error:

1.Check the path to the vaderetro.so library file. Change the path, if necessary (the VaderetroLibPath parameter in the [Root] section of the configuration file).

In order to view and correct the path, you may use the commands of the command line management tool.

•To view current parameter value, execute the command

$ drweb-ctl cfshow Root.VaderetroLibPath

•To set a new parameter value, execute the command

# drweb-ctl cfset Root.VaderetroLibPath <new path>

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

# drweb-ctl cfset Root.VaderetroLibPath -r

2.Update virus databases in one of the following ways:

•Click Update on the update control page of the main window of the application.

•Click Update in the context menu of the status indicator in the notification area.

•Execute the command:

$ drweb-ctl update

3.If the path is correct and the error persists after updating virus databases, reinstall the drweb-maild package.

4.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

Databases of web resource categories

Error code

x112

Description

Databases of web resource categories are missing.

Resolving the error:

1.Check the path to the database of web resource categories directory. Change the path, if necessary (the DwsDir parameter in the [Root] section of the configuration file).

•In order to view and correct the path, you may use the commands of the command line management tool.

To view current parameter value, execute the command

$ drweb-ctl cfshow Root.DwsDir

To set a new parameter value, execute the command

# drweb-ctl cfset Root.DwsDir <new path>

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

# drweb-ctl cfset Root.DwsDir -r

2.Update virus databases in one of the following ways:

•Click Update on the update control page of the main window of the application.

•Click Update in the context menu of the status indicator in the notification area.

•Execute the command:

$ drweb-ctl update

3.If an error persists, install the package drweb-dws separately. This package contains databases of web resource categories.

4.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

Linux kernel module for SpIDer Gate is unavailable

Error code

x113

Description

SpIDer Gate requires a Linux kernel module which is missing.

Resolving the error:

1.Check which operating mode of the component was selected and change it—if necessary—by setting the value to Auto (for theMode parameter in the [LinuxSpider] section of the configuration file).

In order to view and correct the mode, you 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

2.If the error persists, manually build and install the loadable kernel module for SpIDer Guard

Note that operation of SpIDer Guard and of the loadable kernel module is guaranteed only on the tested Linux distributives (see System Requirements).

If the error persists, contact technical support and be ready to name the error code.

Error message

SpIDer Gate is unavailable

Error code

x117

Description

SpIDer Gate component is missing (required for scanning network connections).

Resolving the error:

1.Check the path to the drweb-gated executable file. Change the path, if necessary (the ExePath parameter in the [GateD] section of the configuration file).

You may use the commands of the command-line management tool.

•To view current parameter value, execute the following command:

$ drweb-ctl cfshow GateD.ExePath

•To set a new parameter value, execute the command

# drweb-ctl cfset GateD.ExePath <new path>

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

# drweb-ctl cfset GateD.ExePath -r

2.If the configuration does not contain settings for SpIDer Gate component or if the error persists after entering the correct path, install or reinstall the drweb-gated package.

3.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

MailD is not available

Error code

x118

Description

Dr.Web MailD component is missing (it is necessary for scanning email).

Resolving the error:

1.Check the path to the drweb-maild executable file. Change the path, if necessary (the ExePath parameter in the [MailD] section of the configuration file).

You may use the commands of the command-line management tool.

•To view current parameter value, execute the following command:

$ drweb-ctl cfshow MailD.ExePath

•To set a new parameter value, execute the command

# drweb-ctl cfset MailD.ExePath <new path>

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

# drweb-ctl cfset MailD.ExePath -r

2.If the configuration does not contain settings for Dr.Web MailD component or if the error persists after entering the correct path, install or reinstall the drweb-maild package.

3.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

Scanning Engine is not available

Error code

x119

Description

Cannot check files as ScanEngine component (drweb-se) is missing or failed to start. This module is used for searching malicious objects.
Failed to start: Scanner, SpIDer Guard, SpIDer Gate (partially).

Resolving the error:

1.Check the path to the drweb-se executable file. Change the path, if necessary (the ExePath parameter in the [ScanEngine] section of the configuration file).

You may use the commands of the command-line management tool.

•To view current parameter value, execute the following command:

$ drweb-ctl cfshow ScanEngine.ExePath

•To set a new parameter value, execute the command

# drweb-ctl cfset ScanEngine.ExePath <new path>

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

# drweb-ctl cfset ScanEngine.ExePath -r

2.If the error persists after entering the correct path

•Execute the command

$ drweb-ctl rawscan /

If the line Error: No valid license provided, is output, a valid key file is missing. Register the program and receive a license. After receiving the license, check whether the key file is available and install it, if necessary.

•If you use 64-bit version of the operating system, make sure that 32-bit application support libraries are installed (see System Requirements) and, if necessary, install them.

To check that the 32-bit application support library is installed, use the following command:

$ dpkg -l | grep <libname>

where <libname> is name of the library (libc6-i386 or glibc.i686, depending on your system). If the command does not output any result to screen, you should install the library, using the system package manager. In other case, the library is already installed and drweb-se module unavailable due to other reasons.

After you install the library, restart Dr.Web for Linux by the following command:

# service drweb-configd restart

•If your operating system uses SELinux, configure the security policy for the drweb-se module (see section Configuring SELinux Security Policies).

3.If the configuration does not contain the component settings or if the steps previously mentioned do not help, install or reinstall the drweb-se package.

4.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

Scanner is unavailable

Error code

x120

Description

Cannot check files as a Scanner component drweb-filecheck, used for this function, is missing.
Failed to start: Scanner, SpIDer Guard.

Resolving the error:

1.Check the path to the drweb-filecheck executable file. Change the path, if necessary (the ExePath parameter in the [FileCheck] section of the configuration file).

You may use the commands of the command-line management tool.

To view current parameter value, execute the following command:

$ drweb-ctl cfshow FileCheck.ExePath

To set a new parameter value, execute the command

# drweb-ctl cfset FileCheck.ExePath <new path>

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

# drweb-ctl cfset FileCheck.ExePath -r

2.If the error persists after entering the correct path

•If you use 64-bit version of the operating system, make sure that 32-bit application support libraries are installed (see System Requirements) and, if necessary, install them.

To check that the 32-bit application support library is installed, use the following command:

$ dpkg -l | grep <libname>

After you install the library, restart Dr.Web for Linux by the following command:

# service drweb-configd restart

•If your operating system uses SELinux, configure the security policy for the drweb-filecheck module (see section Configuring SELinux Security Policies).

3.If the configuration does not contain the component settings or if the steps previously mentioned do not help, install or reinstall the drweb-filecheck package.

4.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

ES Agent is not available

Error code

x121

Description

Dr.Web ES Agent component is missing (it is necessary to connect to the central protection server).

Resolving the error:

1.Check the path to the drweb-esagent executable file. Change the path, if necessary (the ExePath parameter in the [ESAgent] section of the configuration file).

You may use the commands of the command-line management tool.

•To view current parameter value, execute the following command:

$ drweb-ctl cfshow ESAgent.ExePath

•To set a new parameter value, execute the command

# drweb-ctl cfset ESAgent.ExePath <new path>

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

# drweb-ctl cfset ESAgent.ExePath -r

2.If the configuration does not contain settings for the component or if the error persists after entering the correct path, install or reinstall the drweb-esagent package.

3.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

Firewall for Linux is not available

Error code

x122

Description

Cannot control network connections as drweb-firewall is missing or failed to start. The module is used to divert connections.
Failed to start: SpIDer Gate.

Resolving the error:

1.Check the path to the drweb-firewall executable file. Change the path, if necessary (the ExePath parameter in the [LinuxFirewall] section of the configuration file).

You may use the commands of the command-line management tool.

•To view current parameter value, execute the following command:

$ drweb-ctl cfshow LinuxFirewall.ExePath

•To set a new parameter value, execute the command

# drweb-ctl cfset LinuxFirewall.ExePath <new path>

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

# drweb-ctl cfset LinuxFirewall.ExePath -r

2.If the configuration does not contain settings for Dr.Web Firewall for Linux or if the error persists after entering the correct path, install or reinstall the drweb-firewall package.

3.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

Network Checker is not available

Error code

x123

Description

Cannot control network connections as drweb-netcheck is missing or failed to start. The module is used to check the downloaded files.
Failed to start: SpIDer Gate (partially).

Resolving the error:

1.Check the path to the drweb-netcheck executable file. Change the path, if necessary (the ExePath parameter in the [Netcheck] section of the configuration file).

You may use the commands of the command-line management tool.

•To view current parameter value, execute the following command:

$ drweb-ctl cfshow Netcheck.ExePath

•To set a new parameter value, execute the command

# drweb-ctl cfset Netcheck.ExePath <new path>

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

# drweb-ctl cfset Netcheck.ExePath -r

2.If the configuration does not contain settings for the component or if the error persists after entering the correct path, install or reinstall the drweb-netcheck package.

3.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Error message

CloudD is not available

Error code

x124

Description

The Dr.Web CloudD component (required to request to the Dr.Web Cloud service) is missing.

Resolving the error:

1.Check the path to the drweb-cloudd executable file. Change the path, if necessary (the ExePath parameter in the[CloudD] section of the configuration file).

You may use the commands of the command-line management tool.

•To view current parameter value, execute the following command:

$ drweb-ctl cfshow CloudD.ExePath

•To set a new parameter value, execute the command

# drweb-ctl cfset CloudD.ExePath <new path>

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

# drweb-ctl cfset CloudD.ExePath -r

2.If the configuration does not contain settings for the component or if the error persists after entering the correct path, install or reinstall the drweb-cloudd package.

3.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support and be ready to name the error code.

Symptoms

After installation of the kernel module of SpIDer Guard, operating system abnormally shuts down with a kernel error «Kernel panic»

Description

SpIDer Guard kernel module cannot operate in the operating system kernel environment (for example, when OS operates in the Xen hypervisor environment).

Resolving the error:

1.Cancel the load of the SpIDer Guard LKM module (the module name is drweb) by adding to the grub loader the following string

drweb.blacklist=yes

to the load settings string of the operating system kernel.

2.When the OS is loaded, uninstall the drweb PSB.Ko kernel module from the /lib/' uname-r '/extra directory of additional kernel modules.

3.Set operation mode for SpIDer Guard to AUTO by executing the following commands:

# drweb-ctl cfset LinuxSpider.Mode AUTO
# drweb-ctl reload

4.Do not use the Xen hypervisor, in case your operating system does not support the fanotify interface or this mode does not allow using SpIDer Guard for the full file system monitoring (relevant for GNU/Linux with mandatory access models, for example, for Astra Linux), making the use of the LKM mode mandatory for the file system monitoring.

If the error persists, contact technical support.

Symptoms

Main window of Dr.Web for Linux is disabled, status indicator in notification area of desktop displays an critical error mark, and drop-down menu contains only one disabled item Loading

Description

Dr.Web for Linux cannot start because core component drweb-configd is not available.

Resolving the error:

1.Uninstall Dr.Web for Linuxby entering the following command:

# service drweb-configd restart

2.If this command returns error message, or has no any effect, install drweb-configd component (package) separately.

3.Also note that this may mean, that PAM authentication is not used in the system. If so, please install and configure it.

4.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support.

Symptoms

1.The status indicator is not displayed in the notification area after the user logged in

2.When trying to execute the command

$ drweb-gui

opens the Dr.Web for Linux main window.

Description

The problem could mean that necessary additional library libappindicator1 is not installed in your system.

Resolving the error:

1.Make sure that the package libappindicator1 is installed in your system by the following command:

# dpkg -l | grep libappindicator1

2.If the command does not output any result to screen, you should install the package, using any available system package manager. After that, log out and then log in again (log in).

3.Also note that this may mean, that PAM authentication is not used in the system. If so, please install and configure it.

4.If the previous actions do not help, uninstall Dr.Web for Linux and then install it again on the system.

For details on how to install and uninstall the product or product components, refer to sections Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux.

If the error persists, contact technical support.

Symptoms

1.After disabling SpIDer Guard, all network connections are broken (outgoing and, may be, incoming via SSH and FTP protocols) and cannot be re-established

2.Search through the NetFilter (iptables) rules using the following command

# iptables-save | grep "comment --comment --comment"

returns non-empty result.

Description

This error is related to the incorrect NetFilter (iptables) operation, which version is earlier than 1.4.15. Because of this internal error, when SpIDer Guard adds the rules with a unique label (comment) to the list of rules, the rules are added incorrectly. As a result, on shutting down, SpIDer Guard cannot delete its rules of diverting connections.

Resolving the error:

1.Enable the SpIDer Guard monitor again

2.If you need SpIDer Guard disabled, remove the incorrect rules of NetFilter (iptables) by the following command

# iptables-save | grep -v "comment --comment --comment" | iptables-restore

Note that the iptables-save and iptables-restore commands require the superuser privileges. To elevate your privileges, you can use the su and sudo commands. Note also that this command removes all rules with the incorrect comments, for example, added by other applications that also perform routing traffic.

Additional information:

•To prevent this problem, it is recommended to upgrade your OS (or, at least, only NetFilter to version 1.4.15 or later one).

•You can also switch the diversion of connections towards SpIDer Guard into the Manual mode in the Dr.Web Firewall’s settings if you want to manually divert connections towards SpIDer Guard by specifying the required rules with the help of the iptables utility (this way is not recommended).

•For details, refer to documentation man: drweb-firewall(1), drweb-gated(1), iptables(8).

If the error persists, contact technical support.

Symptoms

Double click on an icon of a file or a catalog runs the scanning in Dr.Web for Linux.

Description

The graphical shell executed an automatic association of files or catalogs after you selected the action Scan in Dr.Web for Linux.

Resolving the error:

1.Cancel the association between files of one type and Dr.Web for Linux. The associations are registered in the file mimeapps.list or in defaults.list. Files with local settings which were changed in a user profile are stored in the directory ~/.local/share/applications/ or ~/.config/ (these directories are usually appended with the attribute “hidden”).

2.Open the file mimeapps.list or defaults.list with any text editor (note that to edit the files, superuser privileges are required. If necessary, use the command su or sudo).

3.In the file, find the section [Default Applications] and association strings that look as <MIME-type>=drweb-gui.desktop. For example,

[Default Applications]
inode/directory=drweb-gui.desktop
text/plain=drweb-gui.desktop;gedit.desktop

4.If the right part (of the equality) of the association string contains links to other applications except drweb-gui.desktop, remove only the following link from the line: drweb-gui.desktop. If the association contains link only to the application drweb-gui, remove the whole association line.

5.Save the changed file.

Additional information:

•To check the current associations, use the utilities xdg-mime, xdg-open , and xdg-settings (included in the package xdg-utils).

•To read more about the xdg utilities, refer to the documentation man: xdg-mime(1), xdg-open(1), xdg-settings(1).

If the error persists, contact technical support.