Hi all,

I have been using ClamAV for several years with Sendmail, MimeDefang, 
& Spam Assassin on a FreeBSD mail server. Last week I upgraded ClamAV 
to version 0.96.5. One morning shortly after, clamd had stopped and mail was 
tempfailing. I checked the logs and restarted clamd but would like to know 
if others are having a similar problem. 

The relevant portion of the log follows:
Jan 31 00:47:14 mailsys freshclam[73461]: Received signal: wake up
Jan 31 00:47:14 mailsys freshclam[73461]: ClamAV update process started at Mon 
Jan 31 00:47:14 2011
Jan 31 00:47:15 mailsys freshclam[73461]: main.cvd is up to date (version: 53, 
sigs: 846214, f-level: 53, builder: sven)
Jan 31 00:47:16 mailsys freshclam[73461]: Downloading daily-12591.cdiff [100%]
Jan 31 00:47:16 mailsys freshclam[73461]: Downloading daily-12592.cdiff [100%]
Jan 31 00:47:16 mailsys freshclam[73461]: daily.cld updated (version: 12592, 
sigs: 33329, f-level: 58, builder: guitar)
Jan 31 00:47:16 mailsys freshclam[73461]: bytecode.cvd is up to date (version: 
123, sigs: 29, f-level: 58, builder: edwin)
Jan 31 00:47:16 mailsys freshclam[73461]: Database updated (879572 signatures) 
from db.us.clamav.net (IP: 194.47.250.218)
Jan 31 00:47:16 mailsys clamd[73451]: SelfCheck: Database modification 
detected. Forcing reload.
Jan 31 00:47:17 mailsys clamd[73451]: Reading databases from /work/db/clamav
Jan 31 00:47:17 mailsys clamd[73451]: reload db failed: Can't verify database 
integrity
Jan 31 00:47:17 mailsys clamd[73451]: Terminating because of a fatal error.
Jan 31 00:47:17 mailsys clamd[73451]: Pid file removed.
Jan 31 00:47:17 mailsys clamd[73451]: --- Stopped at Mon Jan 31 00:47:17 2011
Jan 31 00:47:17 mailsys clamd[73451]: Socket file removed.
Jan 31 00:47:17 mailsys freshclam[73461]: Clamd successfully notified about the 
update.
Jan 31 00:47:17 mailsys freshclam[73461]: --------------------------------------
<snip>
Jan 31 08:09:20 mailsys clamd[79653]: clamd daemon 0.96.5 (OS: freebsd6.3, 
ARCH: i386, CPU: i386)
Jan 31 08:09:20 mailsys clamd[79653]: Running as user mailnull (UID 26, GID 26)
Jan 31 08:09:20 mailsys clamd[79653]: Log file size limited to 1048576 bytes.
Jan 31 08:09:20 mailsys clamd[79653]: Reading databases from /work/db/clamav
Jan 31 08:09:20 mailsys clamd[79653]: Not loading PUA signatures.
Jan 31 08:09:26 mailsys clamd[79653]: Loaded 878314 signatures.
Jan 31 08:09:26 mailsys clamd[79653]: LOCAL: Unix socket file 
/var/run/av_spam/clamd
Jan 31 08:09:26 mailsys clamd[79653]: LOCAL: Setting connection queue length to 
15
Jan 31 08:09:26 mailsys clamd[79654]: Limits: Global size limit set to 
104857600 bytes.
Jan 31 08:09:26 mailsys clamd[79654]: Limits: File size limit set to 26214400 
bytes.
Jan 31 08:09:26 mailsys clamd[79654]: Limits: Recursion level limit set to 16.
Jan 31 08:09:26 mailsys clamd[79654]: Limits: Files limit set to 10000.
Jan 31 08:09:26 mailsys clamd[79654]: Archive support enabled.
Jan 31 08:09:26 mailsys clamd[79654]: Algorithmic detection enabled.
Jan 31 08:09:26 mailsys clamd[79654]: Portable Executable support enabled.
Jan 31 08:09:26 mailsys clamd[79654]: ELF support enabled.
Jan 31 08:09:26 mailsys clamd[79654]: Mail files support enabled.
Jan 31 08:09:26 mailsys clamd[79654]: OLE2 support enabled.
Jan 31 08:09:26 mailsys clamd[79654]: PDF support enabled.
Jan 31 08:09:26 mailsys clamd[79654]: HTML support enabled.
Jan 31 08:09:26 mailsys clamd[79654]: Self checking every 3600 seconds.
Jan 31 08:09:26 mailsys clamd[79654]: Set stacksize to 1114112

While examining the log I noticed that clamd had initiated a db selfcheck while 
freshclam was in the process of an update. Reviewing older logs, this is the 
first time I could find when that had happened. But today (two days later) 
clamd 
had terminated again with the same timing problem.


Does this mean there is a bug in the process or is there some mechanism to 
prevent 
clamd from doing a db check while freshclam is updating the db?

If so, does that mean I have an error in one of the configuration files?


TIA,
J.J.

                                          
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

Reply via email to