• I'm running Qmail+Qmail-Scanner+ClamAV and get the following error in my mail logs: clamdscan: corrupt or unknown clamd scanner error or memory/resource/perms problem. What's wrong with it?

Most likely clamd is not running at all, or you are running Qmail-Scanner and clamd under a different uid. If you are running Qmail-Scanner as qscand (default setting) you could put User qscand inside your clamd.conf file and restart clamd. Remember to check that qscand can create clamd.ctl (usually located at /var/run/clamav/clamd.ctl). The same applies to the log file. The suggested setup is: put User qscand and AllowSupplementaryGroups in clamd.conf, then add user qscand to group clamav and make the socket dir and the log dir group writable by clamav. Another possible reason for the aforementioned problem is that your softlimit is set too low. Try raising it to 40MB at least.

-- ZhendongXu - 22 Nov 2006

I had the same problem, and found that my clamd had died after the logs had rotated, such that my /var/log/clamav/clamd.log had reverted back from qscand.clamav ownership to clamav.clamav ownership. (I noticed that clamd.log.1 still had qscand.clamav ownership, however.) I don't know exactly where the log is rotated, though, as there is no clamd entry in logrotate.d under Fedora Core 6, at least on my install, so I'm not sure how to actually fix this. I do have User qscand in my clamd.conf, but I'm not sure how to set things so the log rotation doesn't revert my ownership. Suggestions? -- ErichBloodaxe - 26 Feb 2007

For all available options logrotate can use see the man pages, but for your problem you will need to have this option:

create 640 qscand clamav

In your clamd configuration file for logrotate. This will create the new logfile with the correct permission and allow clamd to continue to be able to write to newly created logfile. For a standard setup you will find the configuration file for logrotate here: "/etc/logrotate.d/clamd".

-- CraigK - 02 Mar 2007

Having done that, I also checked /var/log/clamav/clamd.log and found

ERROR: Can't save PID in file /var/run/clamav/clamd.pid

I searched around and found someone had suggested changing the permissions for /var/run/clamav to qscand.clamav, so I did that.

Caveats

• To debug permission problems try this: su -s /bin/sh qscand;clamdscan /etc/passwd . It should say "OK".

I am using qmail+qmailscanner. I am getting clamdscan: corrupt or unknown clamd scanner error or memory/resource/perms problem when i test run. Please help me.

</center-->