On Apr 9, 2008, at 4:52 PM, Stephane Durieux wrote:
Hello,
I am encontering a problem with clamsmtp or more exactly with clamav-
daemon.
When I start it, the unix socket used to communicate with clamsmtp
isn t created.
So once lauched in debug mode, clamsmtpd inform me of that problem !
Though, I tried the same configuration on a test server 2 months ago
without any problem.
Could it be a problem of a last update
... Strange ... cause I have updated the boths clam via an official
site
If someone has already encountered that problem and could help me
Thanks for reply
Stephanie,
The socket isn't created immediately - clamav has to read in all the
definitions from its database, which can take awhile. On a dual P3 I
have it takes over 20 minutes sometimes if it reloads everything, and
on a dual Xeon 2.6 with HT, it can take 10 or so minutes to do the
same thing.
If clamsmtp tries to connect it will fail since the socket isn't
created until the database is completely loaded. If this is the case,
just run 'top' and watch the CPU load and the clamav process, which
will probably be eating up most of the CPU time. Also, if you tail /
var/log/clamav/clamav.log, the last line will probably be "<date/time
stamp> -> Reading databases from /var/lib/clamav". When it's done, it
will print out "<date/time stamp -> Database correctly reloaded (xxxxx
signatures)".
hose
