Why does ClamAV show "permanently failed" after enabling the daemon log file?

This error occurs because no valid path for the log file has been specified.

Steps to Resolve

1. Specify the Destination Path and Log File Name Select a destination path and specify a file name for the ClamAV daemon log file.

Example: C:\Users\user.name\Desktop\AV\clamav.log

2. Update Configuration Navigate to MetaDefender Core > ClamAV > Configuration and update the Path of the ClamAV daemon log file with the chosen path and file name.

3. Re-enable the ClamAV Engine After saving the changes, disable the ClamAV engine and then re-enable it. This forces the daemon to reinitialize with the updated configuration.

The daemon log file is particularly useful for troubleshooting issues specific to the ClamAV engine, while the oms_clamav.log focuses on MetaDefender Core’s operations.