Clamav Ping Timeout During Update

[Rick Cooper]

 > -----Original Message-----
 > From: mailscanner-bounces at lists.mailscanner.info 
 > [mailto:mailscanner-bounces at lists.mailscanner.info] On 
 > Behalf Of Julian Field
 > Sent: Monday, March 03, 2008 12:57 PM
 > To: MailScanner discussion
 > Subject: Re: Clamav Ping Timeout During Update
 > 
 > -----BEGIN PGP SIGNED MESSAGE-----
 > Hash: SHA1
 > 
 > 
 > 
 > Neal Morgan wrote:
 > > Greetings:
 > >
 > > My Mailscanner has been reporting timeouts when clamav updates its
 > > database.  I see entries like this in syslog:
 > >
 > > 2008-03-03 08:41:10.000	Server-05	MailScanner[20773]:
 > > Clamd::ERROR:: CLAM PING TIMED OUT! :: .
 > >
 > >
 > > If I review the clamav log, it seems that the timeout always occurs
 > > within several seconds of the "database reloaded" entry:
 > >
 > > Mon Mar  3 08:30:21 2008 -> SelfCheck: Database 
 > modification detected.
 > > Forcing reload.
 > > Mon Mar  3 08:30:21 2008 -> Reading databases from /var/lib/clamav
 > > Mon Mar  3 08:41:09 2008 -> Database correctly reloaded (223704
 > > signatures)
 > >   
 > The ping timeout is set to 90 seconds. This should be way 
 > more than is 
 > needed for a database reload. You are welcome to try 
 > increasing it, look 
 > for the setting of the variable "PingTimeOut" in SweepViruses.pm.
 > 
 > >

I would think MailScanner wouldn't even bother to monitor the database files
if not using ClamAVModule as clamd handles reloading upon updates and
MailScanner shouldn't care because it's not going to load them anyway. It
kind of makes me wonder if he is running both clamd and clamavmodule

Rick


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.