Dr.Web Daemon testing and diagnostics |
If no problems occurred during initialization, Dr.Web Daemon is ready to use. To ensure that the daemon is initialized correctly, use the following command: $ netstat -a and check whether required sockets are created. TCP sockets: . . . Unix socket: . . . Missing of the required sockets in the list indicates problems with Dr.Web Daemon initialization. To perform a functional test and obtain service information, use Dr.Web Daemon console client (drwebdc). TCP sockets: $ drwebdc -nHOSTNAME -pPORTNUM -sv -sb Unix socket: $ drwebdc -uSOCKETFILE -sv -sb Report, similar to the following example, is output to the console: - Version: DrWeb Daemon 6.00 If the report was not output, run extended diagnostics. For TCP socket: $ drwebdc -nHOSTNAME -pPORTNUM -sv -sb -v For UNIX socket: $ drwebdc -uSOCKETFILE -sv -sb -v More detailed report can help to identify the problem: dwlib: fd: connect() failed - Connection refused You can test Dr.Web Daemon with the special eicar.com program included in the installation package. Use any text editor to transform readme.eicar into eicar.com (see instructions within the file). For TCP-socket: $ drwebdc -n<HOST> -p<PORT> eicar.com For UNIX socket: $ drwebdc -u<SOCKETFILE> eicar.com The following result are output: Results: daemon return code 0x20 If the results were not output, check Dr.Web Daemon log file to see whether the file was scanned. If the file was not scanned, run extended diagnostic (see above). If file was scanned successfully, Dr.Web Daemon is fully operational.
|