Fortinet Document Library

Version:

Version:


Table of Contents

Download PDF
Copy Link

Troubleshooting long pending queue

If you have a long pending queue and the scan is not processing or processing slowly, check the following:

  1. View the logs to check if the scan is still processing with errors. If it is, it usually means most jobs entered VM and the Scan Profile should be adjusted.

    Log & Report > File Scan Summary Report > Top File Type > Scanned by Sandboxing can give you hints about which file type should skip sandboxing.

  2. You can also go to Scan Input > Job Queue to see which is the longest queue. Click Load Chart of each VM type to see if it is saturated. If it is saturated, allocate a higher clone # to it.
  3. View the logs to see if there are VM related errors. VM related errors might mean VM clones are corrupted and cannot be recovered.

    In this case, the clones need to be rebuilt. To do that, change any clone number in VM Images and click Apply. Wait a few moments and change the clone number back and click Apply again.

If the above does not resolve the issue, you need advanced troubleshooting that require a debug package. Contact technical support at https://support.fortinet.com,

Troubleshooting long pending queue

If you have a long pending queue and the scan is not processing or processing slowly, check the following:

  1. View the logs to check if the scan is still processing with errors. If it is, it usually means most jobs entered VM and the Scan Profile should be adjusted.

    Log & Report > File Scan Summary Report > Top File Type > Scanned by Sandboxing can give you hints about which file type should skip sandboxing.

  2. You can also go to Scan Input > Job Queue to see which is the longest queue. Click Load Chart of each VM type to see if it is saturated. If it is saturated, allocate a higher clone # to it.
  3. View the logs to see if there are VM related errors. VM related errors might mean VM clones are corrupted and cannot be recovered.

    In this case, the clones need to be rebuilt. To do that, change any clone number in VM Images and click Apply. Wait a few moments and change the clone number back and click Apply again.

If the above does not resolve the issue, you need advanced troubleshooting that require a debug package. Contact technical support at https://support.fortinet.com,