Thanks for your fast answer.
But nope, clamd.conf pointing with LocalSocket to /var/run/clamav/clamd.ctl.
So no mistake here.
Now i tried the following (it seems to help, but maybe just temporarily? Have to wait a few days...):
To guarantee that the scanner has write-access i did:
chmod -R 750 /var/lib/amavis
Then i looked whether the amavis and clamav users were in the right groups. It seems that amavis might have some probs in accessing clamav-directories,...
So i tried to change the user from clamav to amavis:
In /etc/clamav/clamd.conf i changed User clamav
to User amavis
And because clamav has files in
(if not made other configurations)
I changed the user and the group:
chown -R amavis:amavis /var/run/clamav
(The same with clamav in /var/log and /var/lib.)
Then I edited the /etc/clamav/freshclam.conf
, changed it to DatabaseOwner amavis
For all those who have logrotate: I also had a look at
as well as
create 640 clamav adm
to create 640 amavis adm
Then i force-reloaded /etc/init.d/clamav-daemon
Now the error seems gone (from 2 A.M. on till now, just a few hours), but i'm not sure whether it re-appears or not.
Maybe it would be a smarter solution to just add the user amavis to the clamav-group. But didn't try that, because found that "step-by-step"-howto on the net and tried that first. (see http://www200.pair.com/mecham/spam/c...avisd-new.html
So maybe it helps someone, maybe not, depends on what will happen to my log-file ;-)