New Dapper Install

[Scott Kitterman]

On Wednesday 26 July 2006 08:04, Me - Atlantic wrote:
> [snip]
>
> > What I find when I look in that file is:
> >
> > DatabaseMirror db.local.clamav.net
> > DatabaseMirror database.clamav.net
> >
> > Looking in my logs, db.local is working:
> >
> > Database updated (62376 signatures) from db.local.clamav.net (IP:
> > 128.121.60.235)
> > Clamd successfully notified about the update.
>
> looking in /var/log/clamav/freshclam.log , I see the usual warning about
> clamav being outdated, and then this -
> Database updated (62850 signatures) from db.local.clamav.net (IP:
> 63.166.28.8)
> ERROR: Clamd was NOT notified: Can't connect to clamd
> through /var/run/clamav/clamd.ctl
>
> Then a second block of entries (very similar to the first) without the
> error, telling me that main.cvd and daily.cvd are up to date.
>
> I assume that the first block of log entries was made on installation,
> but an nslookup of that IP address produces - ** server can't find
> 8.28.165.63.in-addr-arpa: NXDOMAIN
>
> Does my dns server need a refresh or are the addresses for the freshclam
> database updates specifically 'hidden' ?

The way I read that (I'm not an expert) is that it downloaded the update, but 
couldn't notify clamav:

ERROR: Clamd was NOT notified: Can't connect to clamd 
through /var/run/clamav/clamd.ctl

So, I think from a network perspective, you are OK.  The update was retrieved.  
It appears that what you have now is a clamav issue that's internal to your 
box.

Scott K