In this appendix
•Recommendations for Error Identification
•Error Codes
•Errors without Code
|
If you encounter an error that is not described in this section, please contact technical support. Be ready to name the error code and describe steps to reproduce the issue.
|
Recommendations for Error Identification
•To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the following command:
•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, run the following commands:
# drweb-ctl cfset Root.Log <path to log file>
# drweb-ctl cfset Root.DefaultLogLevel DEBUG
|
•To return to the default logging method and verbosity level, execute the commands:
# drweb-ctl cfset Root.Log -r
# drweb-ctl cfset Root.DefaultLogLevel -r
|
Errors Codes
Error message: Error on monitor channel
|
Error code: x1
Internal designation: EC_MONITOR_IPC_ERROR
Description: One or several components cannot connect with the Dr.Web ConfigD configuration daemon.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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 Dr.Web for UNIX File Servers settings to the defaults.
To do this, 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 Dr.Web for UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Operation is already in progress
|
Error code: x2
Internal designation: EC_ALREADY_IN_PROGRESS
Description: The operation is already in progress.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Wait until operation is finished. If necessary, repeat the required action later. |
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
Internal designation: EC_IN_PENDING_STATE
Description: The requested operation is in pending state.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Wait for the operation to start. If necessary, repeat the required action later. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Interrupted by user
|
Error code: x4
Internal designation: EC_INTERRUPTED_BY_USER
Description: The action has been terminated by the user.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Repeat the required action later. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Operation canceled
|
Error code: x5
Internal designation: EC_CANCELED
Description: The action has been canceled.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Repeat the required action later. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: IPC connection terminated
|
Error code: x6
Internal designation: EC_LINK_DISCONNECTED
Description: An inter-process communication (IPC) connection with one of the Dr.Web for UNIX File Servers components has terminated. It must have shut down after being idle for a long time.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.If the operation is not finished, repeat it later. Otherwise, the termination is not an error. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Invalid IPC message size
|
Error code: x7
Internal designation: EC_BAD_MESSAGE_SIZE
Description: A message of invalid size has been received during component inter-process communication (IPC).
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Reload Dr.Web for UNIX File Servers by entering the command:
# service drweb-configd restart
|
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Invalid IPC message format
|
Error code: x8
Internal designation: EC_BAD_MESSAGE_FORMAT
Description: A message of invalid format has been received during component inter-process communication (IPC).
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Reload Dr.Web for UNIX File Servers by entering the command:
# service drweb-configd restart
|
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Not ready
|
Error code: x9
Internal designation: EC_NOT_READY
Description: The required action cannot be performed because the necessary component or device has not been initialized yet.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Repeat the required action later. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Component is not installed
|
Error code: x10
Internal designation: EC_NOT_INSTALLED
Description: The required operation cannot be performend because the necessary component has not been installed yet.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Install or reinstall the necessary component. If you do not know the component name, try to determine it reviewing the log file.
2.If the installation or reinstallation of the necessary component does not help, reinstall Dr.Web for UNIX File Servers.
For details on how to install and uninstall Dr.Web for UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Unexpected IPC message
|
Error code: x11
Internal designation: EC_UNEXPECTED_MESSAGE
Description: An unexpected message is received during component inter-process communication (IPC).
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Reload Dr.Web for UNIX File Servers by entering the command:
# service drweb-configd restart
|
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: IPC protocol violation
|
Error code: x12
Internal designation: EC_PROTOCOL_VIOLATION
Description: Protocol violation has occurred during component inter-process communication (IPC).
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Reload Dr.Web for UNIX File Servers by entering the command:
# service drweb-configd restart
|
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Subsystem state is unknown
|
Error code: x13
Internal designation: EC_UNKNOWN_STATE
Description: The required operation cannot be performed because one or more subsystems of Dr.Web for UNIX File Servers are in unknown state.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Repeat the operation.
2.If the error persists, restart Dr.Web for UNIX File Servers 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: Path must be absolute
|
Error code: x20
Internal designation: EC_NOT_A_DIRECTORY
Description: A relative path to a file or directory is specified whereas an absolute path is required.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Change the path to the file or directory so as to make the path absolute. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Not enough memory
|
Error code: x21
Internal designation: EC_NO_MEMORY
Description: There is not enough memory to complete the requested operation.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Increase size of available memory for Dr.Web for UNIX File Servers processes (for example, by changing the limits with the ulimit command), restart Dr.Web for UNIX File Servers and repeat the operation.
|
In some cases, the system service systemd can ignore the specified limit changes. In this case, edit (or create if it does not exist) a file /etc/systemd/system/drweb-configd.service.d/limits.conf and specify the changed limit value, for example:
[Service]
LimitDATA=32767
|
|
The list of available limits of systemd can be viewed in the documentation man systemd.exec.
Restart Dr.Web for UNIX File Servers by entering the command:
# service drweb-configd restart
|
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: I/O error
|
Error code: x22
Internal designation: EC_IO_ERROR
Description: An input/output (I/O) error has occurred.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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: No such file or directory
|
Error code: x23
Internal designation: EC_NO_SUCH_ENTRY
Description: The specified object of the file system (file or directory) is missing. It may have been removed.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Check the path. If necessary, change 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
Internal designation: EC_PERMISSION_DENIED
Description: The component cannot access the specified file or directory. It may not have the required permission to access the item.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Check whether the path is correct and whether the component has the required permissions. If it is necessary to access the object, change access permissions or elevate component permissions. Repeat the operation. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Not a directory
|
Error code: x25
Internal designation: EC_NOT_A_DIRECTORY
Description: The specified object of the file system is not a directory.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Check the path. Specify the correct path and 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
Internal designation: EC_NOT_A_DIRECTORY
Description: The requested data is corrupted.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Repeat the operation.
2.If the error persists, restart Dr.Web for UNIX File Servers 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: File already exists
|
Error code: x27
Internal designation: EC_FILE_EXISTS
Description: There is already the file with the same name in the specified location.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Check the path. Change it and 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
Internal designation: EC_READ_ONLY_FS
Description: The file system object (a file, a directory or a socket) that you are trying to modify is read-only.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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
Internal designation: EC_NETWORK_ERROR
Description: A network error has occurred.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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 drive
|
Error code: x30
Internal designation: EC_NOT_A_DRIVE
Description: The I/O device being accessed is not a drive.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Check the device name. Change the path so that it indicate to the drive and repeat the operation. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Unexpected EOF
|
Error code: x31
Internal designation: EC_UNEXPECTED_EOF
Description: The end of file has been reached enexpectedly when reading data.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Check the name of the file. If necessary, change the path so that it indicates the correct file and repeat the operation. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: File was changed
|
Error code: x32
Internal designation: EC_FILE_WAS_CHANGED
Description: The file being scanned has been modified.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Repeat scanning. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Not a regular file
|
Error code: x33
Internal designation: EC_NOT_A_REGULAR_FILE
Description: The object being accessed is not a regular file (it may a directory, a socket, etc.).
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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: Name already in use
|
Error code: x34
Internal designation: EC_NAME_ALREADY_IN_USE
Description: The object cannot be created as there is an object with the same name in the file system.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Check the path. Change it and repeat the operation. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Host is offline
|
Error code: x35
Internal designation: EC_HOST_OFFLINE
Description: A remote host cannot be accessed via the network.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Check whether the required host is available. If necessary, change the host address and repeat the operation. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Resource limit reached
|
Error code: x36
Internal designation: EC_LIMIT_REACHED
Description: The limit defined for the use of a certain resource has been reached.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Check the availability of the required resource. If necessary, raise the limit on the use of this resource and repeat the operation. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Different mount points
|
Error code: x37
Internal designation: EC_CROSS_DEVICE_LINK
Description: The file cannot be restored as restoring implies moving it between two different mountain points.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Choose another path for the file restoration and repeat the operation. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Unpacking error
|
Error code: x38
Internal designation: EC_UNPACKING_ERROR
Description: Archive unpacking failed.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Make sure that the archive is not corrupted. If the archive is protected with password, remove the protection by entering the correct password 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
Internal designation: EC_BASE_CORRUPTED
Description: Virus databases are corrupted.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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 change the path, go to the General Settings page of the web interface, if installed.
•You also can 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:
•click Update on the Main page of the web interface, if installed;
•or execute the command:
|
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
Internal designation: EC_OLD_BASE_VERSION
Description: Current virus databases are designed for an earlier program version.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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 change the path, go to the General Settings page of the web interface, if installed.
•You also can 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:
•click Update on the Main page of the web interface, if installed;
•or execute the command:
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Empty virus database
|
Error code: x42
Internal designation: EC_EMPTY_BASE
Description: Virus databases are empty.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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 change the path, go to the General Settings page of the web interface, if installed.
•You also can 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:
•click Update on the Main page of the web interface, if installed;
•or execute the command:
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Object cannot be cured
|
Error code: x43
Internal designation: EC_CAN_NOT_BE_CURED
Description: The Cure action has been applied to an incurable object.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Select an action that can be applied to the object and repeat the operation. |
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
Internal designation: EC_INVALID_BASE_SET
Description: The current combination of virus databases cannot be supported.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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 change the path, go to the General Settings page of the web interface, if installed.
•You also can 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:
•click Update on the Main page of the web interface, if installed;
•or execute the command:
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Scan limit reached
|
Error code: x45
Internal designation: EC_SCAN_LIMIT_REACHED
Description: The specified limits have been exceeded during the scanning of the object.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Change limits for scanning (in the component settings) by any of the following methods:
•on the page with the component settings on the web interface (if it is installed);
•use the drweb-ctl cfshow and drweb-ctl cfset commands.
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: Authentication failed
|
Error code: x47
Internal designation: EC_AUTH_FAILED
Description: Invalid user credentials have been used for authentication.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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: Authorization failed
|
Error code: x48
Internal designation: EC_NOT_AUTHORIZED
Description: The user does not have enough rights to perform the requested operation.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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: Access token is invalid
|
Error code: x49
Internal designation: EC_INVALID_TOKEN
Description: One of Dr.Web for UNIX File Servers components provides invalid authorization token on attempt to access the operation, requiring elevated privileges.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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: Invalid argument
|
Error code: x60
Internal designation: EC_INVALID_ARGUMENT
Description: An invalid argument has been used when trying to execute a command.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Repeat the required action again using valid argument. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Invalid operation
|
Error code: x61
Internal designation: EC_INVALID_OPERATION
Description: An attempt to run an invalid command has been detected.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Repeat the required action again using valid command. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Superuser privileges required
|
Error code: x62
Internal designation: EC_ROOT_ONLY
Description: Superuser privileges are required to perform the action.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Elevate you privileges to root privileges and repeat the required action. To elevate privileges, you can use the commands su and sudo. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Not allowed in centralized protection mode
|
Error code: x63
Internal designation: EC_STANDALONE_MODE_ONLY
Description: The required action can be performed in standalone mode only.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Change Dr.Web for UNIX File Servers operation mode to standalone mode and repeat the operation.
2.To switch Dr.Web for UNIX File Servers to standalone mode:
•clear the Enable centralized protection mode check box on the Centralized protection of the web interface, if installed;
•or execute the command:
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Non-supported OS
|
Error code: x64
Internal designation: EC_NON_SUPPORTED_OS
Description: Dr.Web for UNIX File Servers does not support the operating system installed on the host.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Install the operating system from the list mentioned in system requirements. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Feature not implemented
|
Error code: x65
Internal designation: EC_NOT_IMPLEMENTED
Description: The required features of one or more components are not implemented in the current version.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Restore Dr.Web for UNIX File Servers settings to the defaults.
To do it, clear the contents of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by executing the following commands:
# cp /etc/opt/drweb.com/drweb.ini /etc/opt/drweb.com/drweb.ini.save
# echo "" > /etc/opt/drweb.com/drweb.ini
|
Restart Dr.Web for UNIX File Servers 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
Internal designation: EC_UNKNOWN_SECTION
Description: The configuration file contains parameters unknown or non-supported in the current version of Dr.Web for UNIX File Servers.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Open the <etc_dir>/drweb.ini file in any text editor, remove the line, containing invalid parameter. Save the file and restart the Dr.Web ConfigD configuration daemon by executing the command:
# service drweb-configd restart
|
2.If it does not help, restore Dr.Web for UNIX File Servers 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.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Unknown section
|
Error code: x67
Internal designation: EC_UNKNOWN_SECTION
Description: The configuration file contains sections unknown or non-supported in the current version of Dr.Web for UNIX File Servers.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Open the <etc_dir>/drweb.ini file in any text editor, remove the unknown (non-supported) section. Save the file and restart the Dr.Web ConfigD configuration daemon by executing the command:
# service drweb-configd restart
|
2.If it does not help, restore Dr.Web for UNIX File Servers 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.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Invalid option value
|
Error code: x68
Internal designation: EC_INVALID_OPTION_VALUE
Description: One or more parameters in the configuration file have invalid values.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Set the valid parameter value by any of the following methods:
•on the page with the component settings on the web interface (if it is installed);
•use the drweb-ctl cfshow and drweb-ctl cfset commands.
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 can also restore parameter value to the default.
2.You can also directly edit the configuration file <etc_dir>/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 Dr.Web ConfigD configuration daemon by executing the command:
# service drweb-configd restart
|
3.If the previous steps did not help, restore Dr.Web for UNIX File Servers 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.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Invalid state
|
Error code: x69
Internal designation: EC_INVALID_STATE
Description: Dr.Web for UNIX File Servers or one of the components is in invalid state to complete the required operation.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Repeat the required action later.
2.If the error persists, restart Dr.Web for UNIX File Servers 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
Internal designation: EC_NOT_LIST_OPTION
Description: In the configuration file a list of values is attributed to a single-valued parameter.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Set the valid parameter value by any of the following methods:
•on the page with the component settings on the web interface (if it is installed);
•use the drweb-ctl cfshow and drweb-ctl cfset commands.
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 can also restore parameter value to the default.
2.You can also directly edit the configuration file <etc_dir>/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 Dr.Web ConfigD configuration daemon by executing the command:
# service drweb-configd restart
|
3.If the previous steps did not help, restore Dr.Web for UNIX File Servers 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.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Record not found
|
Error code: x80
Internal designation: EC_RECORD_NOT_FOUND
Description: The threat record is missing (it may have already been proccessed by another Dr.Web for UNIX File Servers component).
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Update the threat list after some time. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Record is in process now
|
Error code: x81
Internal designation: EC_RECORD_BUSY
Description: The record is already being processed by another component.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Update the threat list after some time. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: File has already been quarantined
|
Error code: x82
Internal designation: EC_RECORD_BUSY
Description: On attempt to move the file with the detected threat to quarantine, it is found out that the file is already in quarantine (most likely, another component processed the threat).
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Update the threat list after some time. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Update zone is not provided it the cloud
|
Error code: x83
Internal designation: EC_NO_ZONE_IN_CLOUD
Description: The attempt to update using Dr.Web Cloud turned unsuccessful.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Repeat the required action later. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Update zone is not provided on disk
|
Error code: x84
Internal designation: EC_NO_ZONE_ON_DISK
Description: The attempt to update the virus bases in the offline mode turned unsuccessful.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Make sure that the path to the device used for updating is correct.
2.Make sure that the user under which you try to update the bases has enough read permissions on the directory containing the updates. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Cannot backup before update
|
Error code: x89
Internal designation: EC_BACKUP_FAILED
Description: Prior to downloading the updates from the updates server, an attempt to make a backup copy of the files to be updated failed.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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).
•To view and change the path, go to the Updater page of the web interface (if it is installed).
•You also can use the commands of the command-line management tool.
To view current parameter value, execute the 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:
•click Update on the Main page of the web interface, if installed;
•or execute the command:
3.If the error persists, check whether the user under whose account the Dr.Web Updater 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 specified in the RunAsUser parameter or grant the missing permissions in the directory properties.
4.If the error persists, reinstall the drweb-update package.
For details on how to install and uninstall Dr.Web for UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Invalid DRL file
|
Error code: x90
Internal designation: EC_BAD_DRL_FILE
Description: The integrity of one of the files with the list of update servers has been violated.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Check the path to the file with the list of servers and change the path if necessary (parameters with *DrlDir in section [Update] of configuration file).
•To view and change the path, go to the Updater page of the web interface (if it is installed).
•You also can use the commands of the command-line management tool.
To view the current parameter value, use the command (<*DrlDirPath> needs to be substituted with a specified parameter name. If the parameter name is unclear, refer to all parameter values in the section, skipping the command part in square brackets):
$ drweb-ctl cfshow Update[.<*DrlDir>]
|
To set new parameter value, execute the command (<*DrlDir> needs to be substituted with a specified parameter name):
# drweb-ctl cfset Update.<*DrlDir> <new path>
|
To restore parameter value to the default, execute the command (<*DrlDir> needs to be substituted with a specified parameter name):
# drweb-ctl cfset Update.<*DrlDir> -r
|
2.Update virus databases:
•click Update on the Main page of the web interface, if installed;
•or execute the command:
3.If the error persists, reinstall the drweb-update package.
For details on how to install and uninstall Dr.Web for UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Invalid LST file
|
Error code: x91
Internal designation: EC_BAD_LST_FILE
Description: The integrity of the file with the list of updated virus databases has been violated.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Update virus databases again after some time:
•click Update on the Main page of the web interface, if installed;
•or execute the command:
2.If the error persists, reinstall the drweb-update package.
For details on how to install and uninstall Dr.Web for UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Invalid compressed file
|
Error code: x92
Internal designation: EC_BAD_LZMA_FILE
Description: An integrity violation of the downloaded file containing updates has been detected.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Update virus databases again after some time:
•click Update on the Main page of the web interface, if installed;
•or execute the command:
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Proxy authentication error
|
Error code: x93
Internal designation: EC_PROXY_AUTH_ERROR
Description: The program fails to connect to update servers via the proxy server specified in the settings.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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).
•To view and set the connection parameters, go to the Updater page of the web interface (if it is installed).
•You also can use the commands of the command-line management tool.
To view current parameter value, execute the 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:
•click Update on the Main page of the web interface, if installed;
•or execute the command:
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: No update servers available
|
Error code: x94
Internal designation: EC_NO_UPDATE_SERVERS
Description: The program fails to connect to any of the update servers.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Check whether the network is available. Change network settings, if necessary.
2.If you can access the network only using a proxy server, set parameters to connect to the proxy server (you can set them in the Proxy parameter in the [Update]section of the configuration file).
•To view and set the connection parameters, go to the Updater page of the web interface (if it is installed).
•You also can use the commands of the command-line management tool.
To view current parameter value, execute the 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 network connection parameters (including parameters of proxy server) are correct, but the error occurs, make sure you use the available list of update servers. The list of update servers used is displayed in parameters *DrlDir in [Update] section of configuration file.
|
If parameters *CustomDrlDir indicate the existing correct file of servers list, the servers specified there will be used instead of the servers of the standard update zone (the value specified in the corresponding parameter*DrlDir, is ignored).
|
•To view and set the connection parameters, go to the Updater page of the web interface (if it is installed).
•You also can use the commands of the command-line management tool.
To view the current parameter value, use the command (<*DrlDirPath> needs to be substituted with a specified parameter name. If the parameter name is unclear, refer to all parameter values in the section, skipping the command part in square brackets):
$ drweb-ctl cfshow Update[.<*DrlDir>]
|
To set new parameter value, execute the command (<*DrlDir> needs to be substituted with a specified parameter name):
# drweb-ctl cfset Update.<*DrlDir> <new path>
|
To restore parameter value to the default, execute the command (<*DrlDir> needs to be substituted with a specified parameter name):
# drweb-ctl cfset Update.<*DrlDir> -r
|
4.Update virus databases:
•click Update on the Main page of the web interface, if installed;
•or execute the command:
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Invalid key file format
|
Error code: x95
Internal designation: EC_BAD_KEY_FORMAT
Description: The key file format is violated.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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 and set the path to the key file, go to the General Settings page of the web interface, if installed.
•You also can use the commands of the command-line management tool.
To view current parameter value, execute the 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 section Licensing.
3.To install the key file, you can use the license activation form at the bottom of the Main page of the web interface, if installed.
4.You can view current license options on user 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 already expired
|
Error code: x96
Internal designation: EC_EXPIRED_KEY
Description: The license has expired.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Purchase a new license and install the key file that you will receive. For more details on ways to purchase the license and installation of the key file refer to section Licensing.
2.To install the purchased key file, you can use the license activation form at the bottom of the Main page of the web interface, if installed.
3.You can view current license options on user 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
Internal designation: EC_NETWORK_TIMEDOUT
Description: Network operation timed out (possibly, a remote host stops responding unexpectedly or the required connection fails).
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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: Invalid checksum
|
Error code: x98
Internal designation: EC_BAD_CHECKSUM
Description: The checksum of the downloaded file with updates is corrupted.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Update virus databases again after some time:
•click Update on the Main page of the web interface, if installed;
•or execute the command:
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Invalid trial license
|
Error code: x99
Internal designation: EC_BAD_TRIAL_KEY
Description: The demo key file is invalid (for example, it may have been received from another computer).
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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 section Licensing.
2.To install the purchased key file, you can use the license activation form at the bottom of the Main page of the web interface, if installed.
3.You can view current license options on user 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: Blocked license key
|
Error code: x100
Internal designation: EC_BLOCKED_LICENSE
Description: The license in use is blocked (the terms of use of Dr.Web for UNIX File Servers may be violated).
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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 section Licensing.
2.To install the received key file, you can use the license activation form at the bottom of the Main page of the web interface, if installed.
3.You can view current license options on user 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
Internal designation: EC_BAD_LICENSE
Description: The license is designed for other product or does not allow the operation of Dr.Web for UNIX File Servers components.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Purchase a new license and install the key file that you will receive. For more details on ways to purchase the license and installation of the key file refer to section Licensing.
2.To install the received key file, you can use the license activation form at the bottom of the Main page of the web interface, if installed.
3.You can view current license options on the user 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
Internal designation: EC_BAD_CONFIG
Description: One or more Dr.Web for UNIX File Servers components cannot operate because of incorrect configuration settings.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.If you do not know the name of the component which causes the error, try to determine it by reviewing the log file.
2.If the error is reported by the SpIDer Guard component, the mode which is selected for the component operation is not probably supported by the OS. Check the selected mode and change it, if necessary. You can do it by setting the value AUTO (the Mode parameter in the [LinuxSpider] section of the configuration file).
•To view and change the mode, go to the SpIDer Guard page of the web interface (if it is installed).
•You also can use the commands of the command-line management tool.
To set the value to AUTO, execute the command:
# drweb-ctl cfset LinuxSpider.Mode AUTO
|
To restore the parameter value to the default, execute the command:
# drweb-ctl cfset LinuxSpider.Mode -r
|
•If the error persists, build and install the loadable kernel module for SpIDer Guard manually.
|
Operation of SpIDer Guard and of the loadable kernel module is guaranteed only on the tested UNIX distributions (see section System Requirements and Compatibility in Administrator Manual).
|
3.If the error is reported by another component, restore component settings to the defaults by any of the following methods:
•on the page with the component settings on the web interface (if it is installed);
•use the drweb-ctl cfshow and drweb-ctl cfset commands;
•edit the configuration file manually (delete all parameters from the component section).
4.If the previous steps did not help, restore Dr.Web for UNIX File Servers settings to the defaults.
To do it, clear the contents of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by executing the following commands:
# cp /etc/opt/drweb.com/drweb.ini /etc/opt/drweb.com/drweb.ini.save
# echo "" > /etc/opt/drweb.com/drweb.ini
|
Restart Dr.Web for UNIX File Servers 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
Internal designation: EC_BAD_EXECUTABLE
Description: The executable file of the component is corrupted.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.If you do not know the name of the component which causes the error, try to determine it by reviewing the log file.
2.Check the executable path to the component in the Dr.Web for UNIX File Servers 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.
For details on how to install and uninstall Dr.Web for UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Core engine is not available
|
Error code: x105
Internal designation: EC_NO_CORE_ENGINE
Description: The file of Dr.Web Virus-Finding Engine is missing or unavailable (required for threat detection).
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Check the path to the drweb32.dll scan engine file. Change the path, if necessary (the CoreEnginePath parameter in the [Root] section of the configuration file).
•To view and change the path, go to the General Settings page of the web interface, if installed.
•You also can 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:
•click Update on the Main page of the web interface, if installed;
•or execute the 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 UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: No virus databases
|
Error code: x106
Internal designation: EC_NO_VIRUS_BASES
Description: Virus databases have not been found.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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 change the path, go to the General Settings page of the web interface, if installed.
•You also can 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:
•click Update on the Main page of the web interface, if installed;
•or execute the command:
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Process terminated by signal
|
Error code: x107
Internal designation: EC_APP_TERMINATED
Description: A component has shut down (e.g., because of the user command or being idle).
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.If 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:
•on the page with the component settings on the web interface (if it is installed);
•use the drweb-ctl cfshow and drweb-ctl cfset commands;
•edit the configuration file manually (delete all parameters from the component section).
3.If it did not help, restore Dr.Web for UNIX File Servers settings to the defaults.
To do it, clear the contents of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by executing the following commands:
# cp /etc/opt/drweb.com/drweb.ini /etc/opt/drweb.com/drweb.ini.save
# echo "" > /etc/opt/drweb.com/drweb.ini
|
Restart Dr.Web for UNIX File Servers 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
Internal designation: EC_APP_CRASHED
Description: A component has shut down because of failure.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Repeat the terminated operation.
2.If the component constantly shuts down abnormally, restore its settings to the defaults by any of the following methods:
•on the page with the component settings on the web interface (if it is installed);
•use the drweb-ctl cfshow and drweb-ctl cfset commands;
•edit the configuration file manually (delete all parameters from the component section).
3.If it did not help, restore Dr.Web for UNIX File Servers settings to the defaults.
To do it, clear the contents of the <etc_dir>/drweb.ini file (it is recommended that you make a backup of the configuration file), for example, by executing the following commands:
# cp /etc/opt/drweb.com/drweb.ini /etc/opt/drweb.com/drweb.ini.save
# echo "" > /etc/opt/drweb.com/drweb.ini
|
Restart Dr.Web for UNIX File Servers after clearing the contents of the configuration file by executing the command:
# service drweb-configd restart
|
4.If the error persists after restoring Dr.Web for UNIX File Servers settings, reinstall the component package.
For details on how to install and uninstall Dr.Web for UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Incompatible software detected
|
Error code: x109
Internal designation: EC_INCOMPATIBLE
Description: One or several components of Dr.Web for UNIX File Servers cannot operate properly. There is software that impedes their operation in your system.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Disable or reconfigure the incompatible software so as to prevent any interference with the Dr.Web for UNIX File Servers operation. |
If the error persists, contact technical support and be ready to name the error code.
|
Error message: NSS is not available
|
Error code: x111
Internal designation: EC_NO_LINUX_NSS
Description: SpIDer Guard for NSS component required for checking NSS volumes is missing, unavailable or corrupted.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Check the path to the drweb-nss executable file. Change the path, if necessary (the ExePath parameter in the [NSS] section of the configuration file).
You can use the commands of the command-line management tool.
To view current parameter value, execute the command:
$ drweb-ctl cfshow NSS.ExePath
|
To set a new parameter value, execute the command:
# drweb-ctl cfset NSS.ExePath <new path>
|
To restore the parameter value to the default, execute the command:
# drweb-ctl cfset NSS.ExePath -r
|
2.If the configuration does not contain the settings for SpIDer Guard for NSS component or if the error persists after entering the correct path, install or reinstall the drweb-nss package.
For details on how to install and uninstall Dr.Web for UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Kernel module is not available
|
Error code: x113
Internal designation: EC_NO_KERNEL_MODULE
Description: The Linux kernel module required for the operation of SpIDer Guard is missing.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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).
•To view and change the mode, go to the SpIDer Guard page of the web interface (if it is installed).
•You also can use the commands of the command-line management tool.
To set the value to AUTO, execute the command:
# drweb-ctl cfset LinuxSpider.Mode AUTO
|
To restore the parameter value to the default, execute the command:
# drweb-ctl cfset LinuxSpider.Mode -r
|
2.If the error persists, build and install the loadable kernel module for SpIDer Guard manually.
|
Operation of SpIDer Guard and of the loadable kernel module is guaranteed only on the tested UNIX distributions (see section System Requirements and Compatibility in Administrator Manual).
|
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: MeshD is not available
|
Error code: x114
Internal designation: EC_NO_MESHD
Description: The Dr.Web MeshD component required for load balancing during the scanning of files is missing.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Check the path to the drweb-meshd executable file. Change the path, if necessary (the ExePath parameter in the [MeshD] section of the configuration file).
You can use the commands of the command-line management tool.
To view the current parameter value, execute the command:
$ drweb-ctl cfshow MeshD.ExePath
|
To set a new parameter value, execute the command:
# drweb-ctl cfset MeshD.ExePath <new path>
|
To restore the parameter value to the default, execute the command:
# drweb-ctl cfset MeshD.ExePath -r
|
2.If the configuration does not contain the settings for Dr.Web MeshD component or if the error persists after entering the correct path, install or reinstall the drweb-meshd package.
For details on how to install and uninstall Dr.Web for UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: ScanEngine is not available
|
Error code: x119
Internal designation: EC_NO_SCAN_ENGINE
Description: Dr.Web Scanning Engine component required for threat detection is missing or failed to start.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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 use the commands of the command-line management tool.
To view the current parameter value, execute the 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:
If the line “Error: No valid license provided” is output, a valid key file is missing. Register Dr.Web for UNIX File Servers 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 section Configuring SELinux Security Policies).
3.If the configuration does not contain the Dr.Web Scanning Engine component settings or if the steps previously mentioned do not help, install or reinstall the drweb-se package.
For details on how to install and uninstall Dr.Web for UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: FileCheck is not available
|
Error code: x120
Internal designation: EC_NO_FILE_CHECK
Description: Dr.Web File Checker component required for threat detection is missing or failed to start.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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 use the commands of the command-line management tool.
To view the current parameter value, execute the 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 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 Dr.Web File Checker component settings or if the steps previously mentioned do not help, install or reinstall the drweb-filecheck package.
For details on how to install and uninstall Dr.Web for UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: ESAgent is not available
|
Error code: x121
Internal designation: EC_NO_ESAGENT
Description: Dr.Web ES Agent component necessary to connect to the centralized protection server is missing.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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 use the commands of the command-line management tool.
To view the current parameter value, execute the 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 Dr.Web ES Agent component or if 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 UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: NetChecker is not available
|
Error code: x123
Internal designation: EC_NO_NET_CHECK
Description: Dr.Web Network Checker component required for scanning the downloaded files is missing.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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 use the commands of the command-line management tool.
To view the current parameter value, execute the 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 Dr.Web Network Checker component or if 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 UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: CloudD is not available
|
Error code: x124
Internal designation: EC_NO_CLOUDD
Description: Dr.Web CloudD required for making requests to the Dr.Web Cloud service is missing.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.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 use the commands of the command-line management tool.
To view the current parameter value, execute the 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 Dr.Web CloudD component or if 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 UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support and be ready to name the error code.
|
Error message: Unexpected error
|
Error code: x125
Internal designation: EC_UNEXPECTED_ERROR
Description: An unexpected error has occurred in operation of one of the components.
To identify the possible cause and the circumstances of the error, refer to the Dr.Web for UNIX File Servers log (by default, it is located in the /var/log/syslog file or the /var/log/messages file, depending on OS). Also, you can use the command drweb-ctl log.
Resolving the error
1.Restart Dr.Web for UNIX File Servers by entering the command:
# service drweb-configd restart
|
|
If the error persists, contact technical support and be ready to name the error code.
|
Errors Without Code
Symptoms: After the installation of the SpIDer Guard kernel module, a kernel panic occurs in the system.
Description: SpIDer Guard kernel module cannot operate in the operating system kernel environment (for example, when the OS operates in the Xen hypervisor environment).
Resolving the error
1.Cancel the load of the SpIDer Guard kernel module (kernel module name is drweb) by adding to the grub loader the string:
to the load settings string of the operating system kernel.
2.When the OS is loaded, remove the drweb.ko module from the /lib/`uname-r`/extra directory of additional modules.
3.Set operation mode for SpIDer Guard to AUTO by executing the commands:
# drweb-ctl cfset LinuxSpider.Mode AUTO
# drweb-ctl reload
|
4.If operating system you are using does not support fanotify or this mode does not allow SpIDer Guard usage for full control of a file system and LKM mode usage is obligatory, do not use the Xen hypervisor. |
If the error persists, contact technical support.
|
Symptoms: Such components as Dr.Web ClamD do not scan messages; in the Dr.Web for UNIX File Servers log there are messages Too many open files.
Description: Due to a large data scanning load, Dr.Web Network Checker has exceeded the limit of available file descriptors.
Resolving the error
1.Raise the limit of the number of open file descriptors available to the application via the command ulimit -n (default limit of the descriptor number for Dr.Web for UNIX File Servers is 16384).
|
In some cases the system service systemd can ignore the specified limit changes.
In this case, edit (or create if it does not exist) a file /etc/systemd/system/drweb-configd.service.d/limits.conf and specify the changed limit value:
[Service]
LimitNOFILE=16384
|
The list of available limits of systemd can be viewed in the documentation man systemd.exec.
|
2.Once the limit is changed, restart Dr.Web for UNIX File Servers by executing the command:
# service drweb-configd restart
|
|
If the error persists, contact technical support.
|
Symptoms: The web browser cannot establish connection to Dr.Web management web interface; the components of Dr.Web anti-virus solutions are not in the list of running processes (ps ax | grep drweb); attempt to execute any drweb-ctl <command>, except for drweb-ctl rawscan, results in one of the following errors:
Error: connect: No such file or directory: "<path>/.com.drweb.public"
or
Error: connect: Connection refused: "<path>/.com.drweb.public".
Description: Dr.Web for UNIX File Servers cannot start as the configuration daemon Dr.Web ConfigD is not available.
Resolving the error
1.Execute the command:
# service drweb-configd restart
|
to restart Dr.Web ConfigD and Dr.Web for UNIX File Servers.
2.If this command returns an error message, or has no effect, install drweb-configd component (package) separately.
|
Also this may mean that PAM authentication is not used in the system. If so, please install and configure PAM (Dr.Web for UNIX File Servers cannot operate correctly without PAM).
|
3.If the error persists, remove Dr.Web for UNIX File Servers and then install it again.
For details on how to install and uninstall Dr.Web for UNIX File Servers or its components, refer to sections Installing Dr.Web for UNIX File Servers and Uninstalling Dr.Web for UNIX File Servers.
|
If the error persists, contact technical support.
|
|