Troubleshooting Tip: How to troubleshoot VM scan slow or stuck issue

If the FortiSandbox is encountering a large pending queue or scan is not running or running slowly, follow the procedures below to troubleshoot the issue.

1. Check the VM event logs to verify whether the VM scan is running normally and without errors.
                                              
   

    

2. If no errors are observed, it typically indicates that most jobs have entered the VM scan stage. In this case, it is recommended to adjust the scan profile to perform VM scanning only for critical file types, as VM scanning is resource-intensive, and limiting its scope can help conserve system resources.
                                                                                   
   

    

3. Check the FortiSandbox Job Queue to identify which job type has the highest number of pending jobs. Review the load chart for each VM type to determine whether it is saturated. If saturation is observed, allocate additional clones to that VM type.
                                                              

4. If any errors are reported in the VM event log, it may indicate that the VM clones are in a bad state and cannot be recovered. To rebuild the clones, set the clone number to 0, wait for a while, and then change it back to the desired number to reinitialize the VM clones.