This one time, at band camp, Stephen Gran said:
> This one time, at band camp, Stephen Gran said:
> > You clearly have something wrong with your network arrangement.  The
> > first error message says that freshclam is unable to do a DNS query (odd
> > in and of itself) and the second says that freshclam is unable to
> > digitally verify the databsaes downloaded.  this is more serious - do
> > you have some sort of proxy that may be corrupting the databases, or
> > something else that could be going worng?
> 
> Just a ping to see if you have any additional information.  In the
> meantime, i am going to lower the severity, as yours seems like an
> unusual case, rather than the common occurance.  If you have additional
> information, or just disagree, we can discuss the severity later.

Just another ping.  Can you help me figure out what happened here?  It
is not reproducible for me, and from our (brief) conversation IRC chat
about it, it seems like it was a DNS issue.  From what I can remember,
freshclam couldn't get a DNS reply, and so fell back to HTTP HEAD to
check the version of the database available.  Since you were using a
squid proxy, squid reported service unavailable, and the update check,
and the upgrade, failed.  Since
a) DNS was totally broken
b) you have freshclam in a non-standard install (the default is a
   daemon, which doesn't run a check from postinstall)

I am inclined to close this.  If I haven't heard back from you in a
week, I will.

Thanks,
-- 
 -----------------------------------------------------------------
|   ,''`.                                            Stephen Gran |
|  : :' :                                        [EMAIL PROTECTED] |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |
 -----------------------------------------------------------------

Attachment: signature.asc
Description: Digital signature

Reply via email to