Summary
The NetApp Filer reports that scan requests are lost, even though they are scanned by the VirusScan Enterprise for Storage module and timeout settings are properly configured on both the filer and scanner server. This occurs only with very large files (multiple gigabytes).
Example:
nasbpvsc02@nasbpf02p:vscan.server.completionRequestLost:warning]: CIFS: Vscan server 172.22.66.150 completed a scan request for ONTAP_ADMIN$\vol\FSVOL023\dacipost\BUZON GENERAL\PENDIENTES SIN GESTIONAR 20150325.zip but the original request was not found.
Depending on the case, the filer's VSCAN abort_timeout value is either met or exceeded and you see the following error message on the filer:
"vscan.server.requestTimeout:error : CIFS: Virus scan request to xxx for file xxx timed out. Vscan abort_timeout setting exceeded. Filer will retry this request on other vscan servers, if possible."
The scanner server completes the scan request some time later, after which you see the following error in the filer's messages/syslog file:
"vscan.server.completionRequestLost:warning : CIFS: Vscan server xxx completed a scan request for xxx but the original request was not found."
As a workaround, set the filer's abort_timeout value to "0", so that the filer does not report "Scan Request not found" messages in the filer log. Refer below:
- Syntax
vscan options abort_timeout [ reset | set]
- Description
This command sets/shows the current virus scan abort_timeout value in seconds. The value determines how long the filer will wait for the vscan server to perform a virus scan request. Even if the file is still being scanned, the filer will abort the scan. The filer may deny access to the file if this time period elapses, depending on the setting for the vscan option mandatory_scan. The timeout value may be reset to a NetApp-provided default value. It is also possible to set the timeout. Note that setting the timeout to 0 disables this option. If the abort_timeout setting is 0, the filer will wait forever for a scan to complete as long as the vscan server reports that it is making progress.
For further instructions, read the NetApp documentation.
