How can I fix the error: Parse error at /etc/clamav/clamd.conf Unknown option ScanImage?

The clamav-daemon.service refuses to start with the problem: Unknown option ScanImage or Unknown option ScanImageFuzzyHash

Feb 04 17:31:52 debian-ecodms-Stegmann systemd[1]: clamav-daemon.service: Failed with result 'exit-code'.
Feb 04 17:31:52 debian-ecodms-Stegmann systemd[1]: Starting Clam AntiVirus userspace daemon...
Feb 04 17:31:52 debian-ecodms-Stegmann systemd[1]: Started Clam AntiVirus userspace daemon.
Feb 04 17:31:52 debian-ecodms-Stegmann clamd[3444]: ERROR: Parse error at /etc/clamav/clamd.conf:112: Unknown option ScanImage
Feb 04 17:31:52 debian-ecodms-Stegmann clamd[3444]: ERROR: Can't open/parse the config file /etc/clamav/clamd.conf
Feb 04 17:31:52 debian-ecodms-Stegmann systemd[1]: clamav-daemon.service: Main process exited, code=exited, status=1/FAILURE
Feb 04 17:31:52 debian-ecodms-Stegmann systemd[1]: clamav-daemon.service: Failed with result 'exit-code'.
Feb 04 17:31:52 debian-ecodms-Stegmann systemd[1]: clamav-daemon.service: Start request repeated too quickly.

A bug exists in Warden 5.06 where the new ClamAV 1.4.0 ScanImage and ScanImageFuzzyHash options are being added to the /etc/clamav/clamd.conf but Debian 11 or 12 might only have ClamAV 1.07 installed. 

The Fix is to upgrade ClamAV to 1.4.3

Manually upgrading to ClamAV to 1.4.3 will fix these errors and allow the ClamAV daemon to start again:

apt-get update
apt-get upgrade clamav clamav-base clamav-daemon clamav-freshclam
systemctl restart clamav-daemon
  • ScanImage, ScanImageFuzzyHash
  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

How can I fix the error: "milter-reject: END-OF-MESSAGE from..." in the log and found the AV in error (cannot read /etc/clam.d/scan.conf).

Cloudlinux / Imunify360 added their own version of ClamAV to their repo which accidentally...

How can I fix the error: Can't connect to TCP port 10024 on ::1 [Cannot assign requested address] when trying to start Amavis?

When trying to start Amavis you see this in the mail log: Oct 02 03:20:15 condor3648 systemd[1]:...

How can I fix the error: Error [Contentfilter_Settings_Contentfilter]. Message [[QUARANTINEDIR] must be a valid directory?

This error means that Amavis was not installed correctly. Try running the Warden from the command...

How can I fix the error: host 127.0.0.1[127.0.0.1] said: 552 5.3.4 Declared message size (1208029 B) exceeds size limit for recipient?

You can set the message size limit for Amavis under Settings -> Policy Settings -> Misc...

How can I fix the error: milter-reject: DATA 451 4.7.1 Service unavailable - try again later?

Reject log In the Warden reject log you see the message: Service unavailable - try again later....