MetaDefender Core v4 introduces an option that modifies the behavior of MetaDefender Core when a specific engine fails to scan.
Under normal circumstances, all active engines scan every file. Occasionally, an engine will encounter a file that causes it to crash. When this happens, MetaDefender Core will wait some time for the engine to recover, after which, it will restart the engine. During this time, the engine’s results will be logged as “Failed to scan”.
However, MetaDefender Core can be configured to fail the scan if any of the engines report problems. In other words, it can toss out all partially incomplete scans. This can give the illusion that MetaDefender core is failing to scan large amounts of files.
Disabling this option can be done by:
In your web browser, navigate to the MetaDefender Core Management Console at:http://localhost:8008/ (you may need to login under admin privilege)
On the left menu, navigate to Policy -> Workflow Rules to list all available rules
Click on a rule you are using for the current scan, a window pops up where beside the rule properties all the chosen workflow's options are shown on the different tabs.
Click on Scan tab
Uncheck the option "Scan failure threshold" shown below:
This article applies to MetaDefender Core v4 Windows and Linux
This article was last updated on 2018-03-26