In this section
•Recommendations for Error Identification
|
If the occurred error is not present in this section, it is recommended that you contact our technical support. Be ready to provide the error code and describe steps to reproduce the issue. |
Recommendations for Error Identification
•To identify a possible cause and background of the error, refer to the Dr.Web for Linux log (by default, it is stored in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the following command:
# drweb-ctl log |
•To identify errors, we recommend that you store output of the log in a separate file and enable output of detailed debug information. For that, run the commands:
# drweb-ctl cfset Root.Log <log path> |
•To reset the logging settings to defaults, run the following commands:
# drweb-ctl cfset Root.Log -r |
Error code: x1 Internally used name: EC_MONITOR_IPC_ERROR Description: One or several components cannot connect to the Dr.Web ConfigD configuration daemon. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Restart the configuration daemon:
2.Check whether the authentication mechanism for PAM is installed, configured and operates correctly. If necessary, install and configure it (for details refer to administration manuals for your OS distribution). 3.If PAM is configured correctly and restarting the configuration daemon does not help, reset Dr.Web for Linux settings to defaults. To do this, clear the contents of the <etc_dir>/drweb.ini file (you are recommended to make a backup copy of the configuration file), for example, by running the following commands:
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 Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
||
If the error persists, contact our technical support and provide the error code. |
Error code: x2 Internally used name: EC_ALREADY_IN_PROGRESS Description: The operation is already in progress. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Wait for the operation to finish. If necessary, repeat the required action later. |
If the error persists, contact our technical support and provide the error code. |
Error code: x3 Internally used name: EC_IN_PENDING_STATE Description: An operation requested by the user is in a pending state (possibly, a network connection is currently being established or one of the components is starting and initializing, which may take a long time). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Wait for the operation to start. If necessary, repeat the required action later. |
If the error persists, contact our technical support and provide the error code. |
Error code: x4 Internally used name: EC_INTERRUPTED_BY_USER Description: The action has been terminated by the user (possibly, it was taking a long time). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Repeat the required action later. |
If the error persists, contact our technical support and provide the error code. |
Error code: x5 Internally used name: EC_CANCELED Description: The action has been canceled. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Repeat the required action. |
If the error persists, contact our technical support and provide the error code. |
Error code: x6 Internally used name: EC_LINK_DISCONNECTED Description: An IPC connection to one of the Dr.Web for Linux components has been terminated (possibly, the component was shut down due to being idle or by a user request). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting If the operation did not finish, repeat it later. Otherwise, the connection termination is not an error. |
If the error persists, contact our technical support and provide the error code. |
Error code: x7 Internally used name: EC_BAD_MESSAGE_SIZE Description: A message of an invalid size has been received during component inter-process communication (IPC). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Restart Dr.Web for Linux.
|
|
If the error persists, contact our technical support and provide the error code. |
Error code: x8 Internally used name: EC_BAD_MESSAGE_FORMAT Description: A message of an invalid format has been received during component inter-process communication (IPC). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Restart Dr.Web for Linux.
|
|
If the error persists, contact our technical support and provide the error code. |
Error code: x9 Internally used name: EC_NOT_READY Description: The required action cannot be performed because the necessary component or device has not been initialized yet. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Repeat the required action later. |
If the error persists, contact our technical support and provide the error code. |
Error code: x10 Internally used name: EC_NOT_INSTALLED Description: The component necessary for running the required function is not installed. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Install or reinstall the necessary component. If you do not know the component name, try to determine it from the log file. 2.If the installation or reinstallation of the necessary component does not help, reinstall Dr.Web for Linux. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
If the error persists, contact our technical support and provide the error code. |
Error code: x11 Internally used name: EC_UNEXPECTED_MESSAGE Description: An invalid message has been received during component inter-process communication (IPC). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Restart Dr.Web for Linux by running the following command:
|
|
If the error persists, contact our technical support and provide the error code. |
Error code: x12 Internally used name: EC_PROTOCOL_VIOLATION Description: A protocol violation has occurred during component inter-process communication (IPC). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Restart Dr.Web for Linux by running the following command:
|
|
If the error persists, contact our technical support and provide the error code. |
Error code: x13 Internally used name: EC_UNKNOWN_STATE Description: The required operation cannot be performed because a subsystem of Dr.Web for Linux is in an unknown state. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Repeat the operation. 2.If the error persists, restart Dr.Web for Linux by running the following command:
and repeat the operation afterwards. |
|
If the error persists, contact our technical support and provide the error code. |
Error code: x20 Internally used name: EC_NOT_ABSOLUTE_PATH Description: A relative path to a file or a directory has been specified, whereas an absolute path is required. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Make the file or directory path absolute and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x21 Internally used name: EC_NO_MEMORY Description: Not enough memory to complete the requested operation. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Increase the size of the memory available for Dr.Web for Linux processes (for example, by changing the limits using the ulimit command), restart Dr.Web for Linux and repeat the operation.
Available systemd limits can be determined using the man systemd.exec command. Restart Dr.Web for Linux by running the following command:
|
||||
If the error persists, contact our technical support and provide the error code. |
Error code: x22 Internally used name: EC_IO_ERROR Description: An input/output error has occurred (for example, a disk device has not been initialized yet or a partition of the file system is not available anymore). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Ensure the availability of the required I/O device or partition of the file system and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x23 Internally used name: EC_NO_SUCH_ENTRY Description: An attempt to access a non-existent file or directory has been made. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Check the indicated path. If necessary, correct it and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x24 Internally used name: EC_PERMISSION_DENIED Description: Insufficient privileges to access the specified file or directory. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Ensure that the path is correct and the component has the required privileges. If access to the object is denied, change its permissions or elevate component privileges and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x25 Internally used name: EC_NOT_A_DIRECTORY Description: The specified object of the file system is not a directory. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Check the object path. Specify the correct path and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x26 Internally used name: EC_DATA_CORRUPTED Description: The requested data is corrupted. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Repeat the operation. 2.If the error persists, restart Dr.Web for Linux:
and repeat the operation afterwards. |
|
If the error persists, contact our technical support and provide the error code. |
Error code: x27 Internally used name: EC_FILE_EXISTS Description: A file with the same name already exists. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Check the file path. If necessary, correct it and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x28 Internally used name: EC_READ_ONLY_FS Description: The file system is read-only. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Check the object path. Change it so as to indicate a writable partition of the file system and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x29 Internally used name: EC_NETWORK_ERROR Description: A network error has occurred (possibly, a remote host stopped responding unexpectedly or required connection failed). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Check that the network is available and network settings are correct. If necessary, change the network settings and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x30 Internally used name: EC_NOT_A_DRIVE Description: The input/output device being accessed is not a disk device. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Check the specified device name. Correct the path so as to indicate a disk device and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x31 Internally used name: EC_UNEXPECTED_EOF Description: The end of the file has been reached enexpectedly while reading data. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Check the specified file name. If necessary, correct the path so as to indicate the correct file and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x32 Internally used name: EC_FILE_WAS_CHANGED Description: The file being scanned has been modified. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Repeat scanning. |
If the error persists, contact our technical support and provide the error code. |
Error code: x33 Internally used name: EC_NOT_A_REGULAR_FILE Description: The file system object being accessed is not a regular file (it may a directory, a socket and so on). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Check the specified file name. If necessary, change the path so as to indicate a regular file and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x34 Internally used name: EC_NAME_ALREADY_IN_USE Description: A file with the same name already exists. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Check the specified path. Correct it and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x35 Internally used name: EC_HOST_OFFLINE Description: A remote host cannot be accessed over the network. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Check that the required host is available. If necessary, correct the host address and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x36 Internally used name: EC_LIMIT_REACHED Description: A limit on resource usage has been reached. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Check the availability of the required resource. If necessary, raise the limit on the usage of this resource and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x37 Internally used name: EC_CROSS_DEVICE_LINK Description: Restoring the file implies moving it between two different mount points. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Choose another path for restoring the file and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x38 Internally used name: EC_UNPACKING_ERROR Description: Unable to unpack an archive (it may be password-protected or corrupted). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Make sure that the archive is not corrupted. If the archive is protected with a password, remove the protection having entered the correct password and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x40 Internally used name: EC_BASE_CORRUPTED Description: Virus databases are corrupted. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 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). •You can use the commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.Update virus databases: •run the following command:
|
||||
If the error persists, contact our technical support and provide the error code. |
Error code: x41 Internally used name: EC_OLD_BASE_VERSION Description: Current virus databases are intended for an earlier program version. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 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). •You can use the commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.Update virus databases: •run the following command:
|
||||
If the error persists, contact our technical support and provide the error code. |
Error code: x42 Internally used name: EC_EMPTY_BASE Description: The virus database is empty. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 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). •You can use the commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.Update virus databases: •run the following command:
|
||||
If the error persists, contact our technical support and provide the error code. |
Error code: x43 Internally used name: EC_CAN_NOT_BE_CURED Description: The Cure action has been applied to an incurable object. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Select an action that can be applied to this object and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x44 Internally used name: EC_INVALID_BASE_SET Description:Incompatible virus databases. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 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). •You can use the commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.Update virus databases: •run the following command:
|
||||
If the error persists, contact our technical support and provide the error code. |
Error code: x45 Internally used name: EC_SCAN_LIMIT_REACHED Description: The specified limits have been exceeded during the scanning of an object (for example, on the size of an unpacked file, on the nesting depth and so on). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Change the scanning limits (in the component settings) using the drweb-ctl cfshow and drweb-ctl cfset commands. 2.After changing the settings, repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x47 Internally used name: EC_AUTH_FAILED Description: Invalid user credentials have been used for authentication. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Provide valid credentials of a user having required privileges and try to authenticate again. |
If the error persists, contact our technical support and provide the error code. |
Error code: x48 Internally used name: EC_NOT_AUTHORIZED Description: The current user has insufficient privileges for performing the requested operation. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Provide valid credentials of a user having required privileges and try to authorize again. |
If the error persists, contact our technical support and provide the error code. |
Error code: x49 Internally used name: EC_INVALID_TOKEN Description: A component of Dr.Web for Linux has provided an invalid authorization token in an attempt to execute an operation requiring elevated privileges. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Authenticate by providing valid credentials of a user having required privileges and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x60 Internally used name: EC_INVALID_ARGUMENT Description: Unable to run the command since an invalid argument has been provided. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Check the command syntax and format. 2.Repeat the required action having indicated a valid argument. |
If the error persists, contact our technical support and provide the error code. |
Error code: x61 Internally used name: EC_INVALID_OPERATION Description: An attempt to run an invalid command has been made. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Repeat the required action using a valid command. |
If the error persists, contact our technical support and provide the error code. |
Error code: x62 Internally used name: EC_ROOT_ONLY Description: Superuser privileges are required to perform the required action. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Elevate you privileges to superuser ones and repeat the required action. To elevate the privileges, use the su or sudo command. |
If the error persists, contact our technical support and provide the error code. |
Error code: x63 Internally used name: EC_STANDALONE_MODE_ONLY Description: The required action can be performed only when Dr.Web for Linux operates in standalone mode. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Switch Dr.Web for Linux to the standalone mode and repeat the operation. To switch Dr.Web for Linux to the standalone mode: •run the following command:
|
|
If the error persists, contact our technical support and provide the error code. |
Error code: x64 Internally used name: EC_NON_SUPPORTED_OS Description: Dr.Web for Linux does not support the operating system installed on the host. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Install an operating system from the list provided in system requirements. |
If the error persists, contact our technical support and provide the error code. |
Error code: x65 Internally used name: EC_UNKNOWN_OPTION Description: The required features of the component are not implemented in the current version. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Try to reset the settings of Dr.Web for Linux to defaults. To do this, clear the content of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by running the following commands:
Restart Dr.Web for Linux after clearing the content of the configuration file by running the following command:
|
||
If the error persists, contact our technical support and provide the error code. |
Error code: x66 Internally used name: EC_UNKNOWN_OPTION Description: The configuration file contains parameters that are unknown to or not supported by the current version of Dr.Web for Linux. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Open the <etc_dir>/drweb.ini file in any text editor, remove the line containing the invalid parameter. Save the file and restart the Dr.Web ConfigD configuration daemon by running the command:
2.If this does not help, reset Dr.Web for Linux settings to defaults. To do this, clear the contents of the <etc_dir>/drweb.ini file (it is recommended to make a backup copy of the configuration file first), for example, by running the following commands:
Restart the configuration daemon after clearing the contents of the configuration file. |
||
If the error persists, contact our technical support and provide the error code. |
Error code: x67 Internally used name: EC_UNKNOWN_SECTION Description: The configuration file contains sections unknown to or not supported by the current version of Dr.Web for Linux. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Open the <etc_dir>/drweb.ini file in any text editor, remove the unknown (unsupported) section. Save the file and restart the Dr.Web ConfigD configuration daemon by running the following command:
2.If this does not help, reset Dr.Web for Linux settings to defaults. To do this, clear the contents of the <etc_dir>/drweb.ini file (it is recommended to make a backup copy of the configuration file first), for example, by running the following commands:
Restart the configuration daemon after clearing the contents of the configuration file. |
||
If the error persists, contact our technical support and provide the error code. |
Error code: x68 Internally used name: EC_INVALID_OPTION_VALUE Description: One or more parameters in the configuration file have invalid values. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Set the parameter value using the drweb-ctl cfshow and drweb-ctl cfset commands. If you do not know which value is valid for the parameter, refer to a man page for the component which uses this parameter. You can also restore a default value of the parameter. 2.You can also directly edit the <etc_dir>/drweb.ini configuration file. To do this, open it in any text editor, find the line containing an invalid parameter value, set a valid value, then save the file and restart the Dr.Web ConfigD configuration daemon by running the following command:
3.If the previous steps did not help, reset Dr.Web for Linux settings to defaults. To do this, clear the content of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by running the following commands:
Restart the configuration daemon after clearing the content of the configuration file. |
||
If the error persists, contact our technical support and provide the error code. |
Error code: x69 Internally used name: EC_INVALID_STATE Description: Dr.Web for Linux or one of its components is in an invalid state and cannot complete the required operation. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Repeat the required action later. 2.If the error persists, restart Dr.Web for Linux by running the following command:
|
|
If the error persists, contact our technical support and provide the error code. |
Error code: x70 Internally used name: EC_NOT_LIST_OPTION Description: A list of values is set for a single-valued parameter in the configuration file. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Set the parameter value using the drweb-ctl cfshow and drweb-ctl cfset commands. If you do not know which value is valid for the parameter, refer to a man page for the component which uses this parameter. You can also restore a default value of the parameter. 2.You can also directly edit the <etc_dir>/drweb.ini configuration file. To do this, open it in any text editor, find the line containing an invalid parameter value, set a valid value, then save the file and restart the Dr.Web ConfigD configuration daemon by running the following command:
3.If the previous steps did not help, reset Dr.Web for Linux settings to defaults. To do this, clear the content of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by running the following commands:
Restart the configuration daemon after clearing the content of the configuration file. |
||
If the error persists, contact our technical support and provide the error code. |
Error code: x80 Internally used name: EC_RECORD_NOT_FOUND Description: The threat record is missing (it may have already been proccessed by another component). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Update the threat list later. |
If the error persists, contact our technical support and provide the error code. |
Error code: x81 Internally used name: EC_RECORD_BUSY Description: The threat is already being processed by another component. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Update the threat list later. |
If the error persists, contact our technical support and provide the error code. |
Error code: x82 Internally used name: EC_QUARANTINED_FILE Description: The file is already in quarantine. Probably, another component has already processed the threat. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Update the threat list later. |
If the error persists, contact our technical support and provide the error code. |
Error code: x89 Internally used name: EC_BACKUP_FAILED Description: Prior to downloading updates from an update server, an attempt to make a backup copy of the files to be updated has failed. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Check the path to the directory that stores backup copies of the files to be updated. Change the path, if necessary (the BackupDir parameter in the [Update] section of the configuration file). •To view and change the path, usecommands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.Update virus databases: •run the following command:
3.If the error persists, check whether the user as whom the component is running has write permissions for a directory specified in the BackupDir parameter. The name of this user is specified in the RunAsUser parameter. If necessary, change the user specified in the RunAsUser parameter or grant the lacking permissions in the directory attributes. 4.If the error persists, reinstall the drweb-update package. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
||||
If the error persists, contact our technical support and provide the error code. |
Error code: x90 Internally used name: EC_BAD_DRL_FILE Description: The integrity of one of the files storing a list of update servers is violated. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Check the path to the file storing the list of servers and change the path if necessary (parameters containing *DrlDir in the [Update] section of the configuration file). •Use commands of the command-line management tool. To view the current parameter value, run the following command (replace <*DrlDir> with a specific parameter name. If the parameter name is unknown, view all parameter values in the section, skipping the command part in square brackets):
To set a new parameter value, run the following command (replace <*DrlDir> with a specific parameter name):
To restore the default parameter value, run the following command (replace <*DrlDir> with a specific parameter name):
2.Update virus databases: •run the following command:
3.If the error persists, reinstall the drweb-update package. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
||||
If the error persists, contact our technical support and provide the error code. |
Error code: x91 Internally used name: EC_BAD_LST_FILE Description: The integrity of the file storing a list of virus databases to be updated is violated. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Update virus databases again after some time: •run the following command:
2.If the error persists, reinstall the drweb-update package. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
|
If the error persists, contact our technical support and provide the error code. |
Error code: x92 Internally used name: EC_BAD_LZMA_FILE Description: The integrity of the downloaded file containing updates is violated. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Update virus databases again after some time: •run the following command:
|
|
If the error persists, contact our technical support and provide the error code. |
Error code: x93 Internally used name: EC_PROXY_AUTH_ERROR Description: Unable to connect to update servers via the proxy server specified in the settings. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Check the parameters used to connect to the proxy server (set with the Proxy parameter in the [Update] section of the configuration file). •Use commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.Update virus databases: •run the following command:
|
||||
If the error persists, contact our technical support and provide the error code. |
Error code: x94 Internally used name: EC_NO_UPDATE_SERVERS Description: Unable to connect to any of the update servers. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Check if the network is available. Change network settings if necessary. 2.If you can access the network only using a proxy server, configure connection to the proxy server (the Proxy parameter in the [Update] section of the configuration file). •Use commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
3.If the network connection parameters (including the parameters of the proxy server) are correct, but the error persists, make sure that you use a relevant list of update servers. The list of used update servers is set in *DrlDir parameters in the [Update] section of the configuration file.
•Use commands of the command-line management tool. To view the current parameter value, run the following command (replace <*DrlDir> with a specific parameter name. If the parameter name is unknown, view all parameter values in the section, skipping the command part in square brackets):
To set a new parameter value, run the following command (replace <*DrlDir> with a specific parameter name):
To restore the default parameter value, run the following command (replace <*DrlDir> with a specific parameter name):
4.Update virus databases: •run the following command:
|
|||||||||
If the error persists, contact our technical support and provide the error code. |
Error code: x95 Internally used name: EC_BAD_KEY_FORMAT Description: The key file format is violated. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Check that you have a key file and a correct path to it. You can specify the path to the key file in the KeyPath parameter in the [Root] section of the configuration file. •Use commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.If you do not have a key file or the key file being used is corrupted, purchase and install it. For more details on the key file, purchasing and installing it, refer to the Licensing section. 3.You can view current license options on the My Dr.Web user webpage at https://support.drweb.com/get+cabinet+link/. |
|||
If the error persists, contact our technical support and provide the error code. |
Error code: x96 Internally used name: EC_EXPIRED_KEY Description: The license has expired. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Purchase a new license and install a received key file. For more details on how to purchase the license and install the key file, refer to the Licensing section. 2.You can view current license options on the My Dr.Web user webpage at https://support.drweb.com/get+cabinet+link/. |
If the error persists, contact our technical support and provide the error code. |
Error code: x97 Internally used name: EC_NETWORK_TIMEDOUT Description: A network connection timed out (possibly, a remote host has stopped responding unexpectedly or the required connection has failed). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Check that the network is available and network settings are correct. If necessary, change the network settings and repeat the operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x98 Internally used name: EC_BAD_CHECKSUM Description: The checksum of the downloaded file with updates is invalid. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Update virus databases again after some time: •run the following command:
|
|
If the error persists, contact our technical support and provide the error code. |
Error code: x99 Internally used name: EC_BAD_TRIAL_KEY Description: The demo key file is invalid (for example, it was received for another computer). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Request a new demo period for this computer or purchase a new license and install a received key file. For more details on how to purchase the license and install the key file, refer to the Licensing section. 2.You can view current license options on the My Dr.Web user webpage at https://support.drweb.com/get+cabinet+link/. |
If the error persists, contact our technical support and provide the error code. |
Error code: x100 Internally used name: EC_BLOCKED_LICENSE Description: The current license is blocked (the terms of use of Dr.Web for Linux may be violated). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Purchase a new license and install a received key file. For more details on how to purchase the license and install the key file, refer to the Licensing section. 2.You can view current license options on the My Dr.Web user webpage at https://support.drweb.com/get+cabinet+link/. |
If the error persists, contact our technical support and provide the error code. |
Error code: x101 Internally used name: EC_BAD_LICENSE Description: The license is intended for another product or does not cover Dr.Web for Linux components. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Purchase a new license and install a received key file. For more details on how to purchase the license and install the key file, refer to the Licensing section. 2.You can view current license options on the My Dr.Web user webpage at https://support.drweb.com/get+cabinet+link/. |
If the error persists, contact our technical support and provide the error code. |
Error code: x102 Internally used name: EC_BAD_CONFIG Description: A component of Dr.Web for Linux cannot operate because of invalid configuration settings. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.If you do not know the name of the component that causes the error, try to determine it by viewing the log file. 2.If the error is caused by the SpIDer Guard component, the mode that is selected for the component operation is probably not supported by your operating system. Check the selected component mode and change it, if necessary, by setting the Auto value (the Mode parameter in the [LinuxSpider] section of the configuration file). •Use commands of the command-line management tool. To set the value to Auto, run the following command:
To reset the parameter to its default value, run the command:
If the error persists, build and install the loadable kernel module for SpIDer Guard manually.
3.If the error is caused by another component, reset its settings to defaults using any of the following methods: •using 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, reset Dr.Web for Linux settings to defaults. To do this, clear the content of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by running the commands:
Restart Dr.Web for Linux after clearing the configuration file by running the command:
|
||||||
If the error persists, contact our technical support and provide the error code. |
Error code: x104 Internally used name: EC_BAD_EXECUTABLE Description: Failed to start the component. The executable file is corrupted or the file path is invalid. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.If you do not know the name of the component that causes the error, try to determine it by viewing the log file. 2.Check the executable path to the component in the Dr.Web for Linux configuration file (the ExePath parameter in the component section) by running the following command (replace <component section> with the name of the corresponding section of the configuration file):
3.Reset the path to its default value by running the command (replace <component section> with the name of the corresponding section of the configuration file):
4.If the previous steps did not help, reinstall the package of the corresponding component. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
||
If the error persists, contact our technical support and provide the error code. |
Error code: x105 Internally used name: EC_NO_CORE_ENGINE Description: The file of Dr.Web Virus-Finding Engine is missing or unavailable. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Check the path to the anti-virus engine file drweb32.dll and, if necessary, correct it (the CoreEnginePath parameter in the [Root] section of the configuration file). •Use commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.Update virus databases: •run the following command:
3.If the path is correct and the error persists after updating virus databases, reinstall the drweb-bases package. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
||||
If the error persists, contact our technical support and provide the error code. |
Error code: x106 Internally used name: EC_NO_VIRUS_BASES Description: Virus databases are missing. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 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). •You can use the commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.Update virus databases: •run the following command:
|
||||
If the error persists, contact our technical support and provide the error code. |
Error code: x107 Internally used name: EC_APP_TERMINATED Description: A component has been shut down (possibly, owing to being idle or by a user request). To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.If the operation has not finished, repeat it. Otherwise, the shutdown is not an error. 2.If the component shuts down constantly, reset its settings to default using any of the following methods: •using the drweb-ctl cfshow and drweb-ctl cfset commands; •edit the configuration file manually (delete all parameters from the component section). 3.If this did not help, reset Dr.Web for Linux settings to default. To do this, clear the content of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by running the following commands:
Restart Dr.Web for Linux after clearing the content of the configuration file by running the following command:
|
||
If the error persists, contact our technical support and provide the error code. |
Error code: x108 Internally used name: EC_APP_CRASHED Description: A component has been shut down because of a failure. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Repeat the terminated operation. 2.If the component constantly shuts down abnormally, reset its settings to default using any of the following methods: •using the drweb-ctl cfshow and drweb-ctl cfset commands; •edit the configuration file manually (delete all parameters from the component section). 3.If this did not help, reset Dr.Web for Linux settings to default. To do this, clear the content of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by running the following commands:
Restart Dr.Web for Linux after clearing the content of the configuration file by running the following command:
4.If the error persists after resetting Dr.Web for Linux settings, reinstall the component package. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
||
If the error persists, contact our technical support and provide the error code. |
Error code: x109 Internally used name: EC_INCOMPATIBLE Description: One or several components of Dr.Web for Linux cannot operate properly. Their operation is impeded by software in your system. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Disable or reconfigure the conflicting software such as to prevent any interference in the Dr.Web for Linux operation. |
If the error persists, contact our technical support and provide the error code. |
Error code: x110 Internally used name: EC_BAD_ANTISPAM_LIB Description: A file of the anti-spam library required for e-mail scanning is missing, unavailable or corrupted. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Check the path to the library file and, if necessary, correct it (the AntispamCorePath parameter in the [Root] section of the configuration file). •Use commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.Update virus databases: •run the following command:
3.If the path is correct and the error persists after updating virus databases, reinstall the drweb-maild package. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
||||
If the error persists, contact our technical support and provide the error code. |
Error code: x112 Internally used name: EC_NO_DWS_BASES Description: Databases of web resource categories are missing. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Check the path directory to a database of web resource categories. Change the path if necessary (the DwsDir parameter in the [Root] section of the configuration file). •Use commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.Update databases of web resource categories: •run the command:
|
||||
If the error persists, contact our technical support and provide the error code. |
Error code: x113 Internally used name: EC_NO_KERNEL_MODULE Description: The Linux kernel module required for the operation of SpIDer Guard is missing. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 1.Check which operating mode of the component was selected and change it, if necessary, by setting the value to Auto (for the Mode parameter in the [LinuxSpider] section of the configuration file). •Use commands of the command-line management tool. To set the value to Auto, run the command:
To reset the parameter to its default value, run the command:
2.If the error persists, build and install the loadable kernel module for SpIDer Guard manually.
|
||||
If the error persists, contact our technical support and provide the error code. |
Error code: x117 Internally used name: EC_NO_GATED Description: The SpIDer Gate component required for scanning network connections is missing. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 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 can also use the commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.If the configuration does not contain SpIDer Gate settings or the error persists after entering the correct path, install or reinstall the drweb-gated package. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
|||
If the error persists, contact our technical support and provide the error code. |
Error code: x118 Internally used name: EC_NO_MAILD Description: The Dr.Web MailD component required for email scanning is missing. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 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 can also use the commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.If the configuration does not contain Dr.Web MailD settings or the error persists after entering the correct path, install or reinstall the drweb-maild package. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
|||
If the error persists, contact our technical support and provide the error code. |
Error code: x119 Internally used name: EC_NO_SCAN_ENGINE Description: The Dr.Web Scanning Engine component required for threat detection is missing or has failed to start. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 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 can also use the commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.If the error persists after entering the correct path: •Run the following command:
If the line “Error: No valid license provided»Error: No valid license provided” is output, a valid key file is missing. Register Dr.Web for Linux and receive a license. After receiving the license, check whether the key file is available and install it if necessary. •If your operating system uses SELinux, configure the security policy for the drweb-se module (see the section Configuring SELinux Security Policies). 3.If the configuration does not contain Dr.Web Scanning Engine settings or the previous steps did not help, install or reinstall the drweb-se package. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
||||
If the error persists, contact our technical support and provide the error code. |
Error code: x120 Internally used name: EC_NO_FILE_CHECK Description: The Dr.Web File Checker component is missing or has failed to start. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 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 can also use the commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.If the error persists after entering the correct path: •If your operating system uses SELinux, configure the security policy for the drweb-filecheck module (see the section Configuring SELinux Security Policies). 3.If the configuration does not contain Dr.Web File Checker settings or the previous steps did not help, install or reinstall the drweb-filecheck package. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
|||
If the error persists, contact our technical support and provide the error code. |
Error code: x121 Internally used name: EC_NO_ESAGENT Description: The Dr.Web ES Agent component required to connect to a centralized protection server is missing. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 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 can also use the commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.If the configuration does not contain Dr.Web ES Agent settings or the error persists after entering the correct path, install or reinstall the drweb-esagent package. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
|||
If the error persists, contact our technical support and provide the error code. |
Error code: x122 Internally used name: EC_NO_FIREWALL Description: The Dr.Web Firewall for Linux component required for scanning network connections is missing. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 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 can also use the commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.If the configuration does not contain Dr.Web Firewall for Linux settings or the error persists after entering the correct path, install or reinstall the drweb-firewall package. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
|||
If the error persists, contact our technical support and provide the error code. |
Error code: x123 Internally used name: EC_NO_NETCHECK Description: The Dr.Web Network Checker component required to scan files over the network is missing. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 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 can also use the commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.If the configuration does not contain Dr.Web Network Checker settings or the error persists after entering the correct path, install or reinstall the drweb-netcheck package. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
|||
If the error persists, contact our technical support and provide the error code. |
Error code: x124 Internally used name: EC_NO_CLOUDD Description: The Dr.Web CloudD component required for making requests to the Dr.Web Cloud service is missing. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting 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 can also use the commands of the command-line management tool. To get the current parameter value, run the command:
To set a new parameter value, run the command:
To reset the parameter to its default value, run the command:
2.If the configuration does not contain Dr.Web CloudD settings or the error persists after entering the correct path, install or reinstall the drweb-cloudd package. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
|||
If the error persists, contact our technical support and provide the error code. |
Error code: x125 Internally used name: EC_UNEXPECTED_ERROR Description: An unexpected error has occurred in operation of one or several components. To identify a possible cause and circumstances of the error, refer to the Dr.Web for Linux log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on the OS). You can also use the drweb-ctl log command. Troubleshooting Restart Dr.Web for Linux by running the command:
|
|
If the error persists, contact our technical support and provide the error code. |
|
Symptoms: After installation of the SpIDer Guard kernel module, the operating system abnormally shuts down with the “Kernel panic” error. Description: The SpIDer Guard kernel module cannot operate in operating system kernel environment (for example, when the OS operates in the Xen hypervisor environment). Troubleshooting 1.Cancel loading of the SpIDer Guard kernel module (named drweb) by adding the following string in the GNU GRUB boot loader:
to the string of kernel boot options. 2.When the OS is loaded, remove the drweb.ko module from the directory /lib/modules/`uname -r`/extra storing additional modules. 3.Set the operation mode of SpIDer Guard to Auto by running the following commands:
4.If your operating system does not support fanotify or this mode does not allow using SpIDer Guard to fully control the file system, and using the LKM mode becomes obligatory, do not use the Xen hypervisor. |
||
If the error persists, contact our technical support. |
|
Symptoms: The main window of Dr.Web for Linux is disabled, the status indicator in the notification area of the taskbar displays a critical error mark, and the drop-down list contains only one disabled item—Loading. Description: Dr.Web for Linux cannot start because the drweb-configd core component is not available. Troubleshooting 1.Restart Dr.Web for Linux by running the command:
2.If this command returns an error or has no effect, install or reinstall the drweb-configd package separately. Note that this may also mean that PAM is not used in the system for user authentication. If so, install and configure it. 3.If the previous actions did not help, uninstall Dr.Web for Linux completely and then install it again. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
|
If the error persists, contact our technical support. |
|
Symptoms 1.The status indicator is not displayed in the notification area after the user has logged in. 2.Running the command to start the graphical interface:
opens Dr.Web for Linux main window. Description: Possibly, this issue is caused by that the required additional library libappindicator1 is not installed in your system. Troubleshooting 1.Make sure that the libappindicator1 package is installed in your system by running the following command:
2.If the command does not output any result to the screen, you should install the package using any available system package manager. After that, log out and then log in again. Note that this may also mean that PAM is not used in the system for user authentication. If so, install and configure it. 3.If the previous actions did not help, uninstall Dr.Web for Linux completely and then install it again. For details on how to install and uninstall Dr.Web for Linux or its components, refer to sections Manual Installing Dr.Web for Linux and Uninstalling Dr.Web for Linux. |
||
If the error persists, contact our technical support. |
|
Symptoms 1.After disabling SpIDer Gate, all network connections (both outgoing and, possibly, incoming via the SSH and FTP) stop working. 2.Searching through NetFilter (iptables) rules using the following command:
returns a non-empty result. Description: This error is related to incorrect operation of NetFilter (iptables) earlier than 1.4.15. The error causes the rules having a unique tag (comment) to be added incorrectly, as a result of which, when shutting down, SpIDer Gate cannot remove its rules for forwarding network connections. Troubleshooting 1.Re-enable SpIDer Gate. 2.If you need to keep SpIDer Gate disabled, remove incorrect NetFilter (iptables) rules by running the command:
Additional Information •To prevent this issue in the future, it is recommended to upgrade your operating system (or at least NetFilter to version 1.4.15 or later). •You can also switch SpIDer Gate to a manual mode of forwarding connections by specifying the required rules manually using the iptables utility (not recommended). •For details, refer to the following man pages: drweb-firewall(1), drweb-gated(1), iptables(8). |
||||
If the error persists, contact our technical support. |
|
Symptoms: Double-clicking an icon of a file or a directory in a graphical file manager starts the scanning in Dr.Web for Linux instead of opening this file or directory. Description: The graphical shell has automatically associated files of a certaing type and/or directories with the Open With Dr.Web for Linux action. Troubleshooting 1.Cancel the association of files of this type with Dr.Web for Linux. The associations are registered in the mimeapps.list or defaults.list file. Files defining local settings changed in a user profile are stored in the ~/.local/share/applications/ or ~/.config/ directory (these directories usually have a “hidden” attribute). 2.Open the mimeapps.list or defaults.list file with any text editor. Note that, to edit the system association file, superuser privileges are required. If necessary, use the su or sudo command. 3.In the file, find the [Default Applications] section and association lines such as <MIME-type>=drweb-gui.desktop, for example:
4.If the right part of the association line (after the equal sign) contains links to other applications besides drweb-gui.desktop, remove only the link to the drweb-gui application (drweb-gui.desktop). If the association contains a link only to the drweb-gui application, remove the whole association line. 5.Save the changed file. Additional information •To check the current associations, use the xdg-mime, xdg-open and xdg-settings utilities (included in the xdg-utils package). •To read more about the xdg utilities, refer to the documentation shown by running the man command: xdg-mime(1), xdg-open(1) and xdg-settings(1). |
|
If the error persists, contact our technical support. |