Hi, Luca, Dennis, and others,
Hello Rolf,
bash-2.05# telnet 62.133.206.90 80
Trying 62.133.206.90...
Connected to 62.133.206.90.
Escape character is '^]'.
quit
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>302 Found</TITLE>
</HEAD><BODY>
<H1>Found</H1>
The document has moved <A HREF="http://www.unnet.nl/";>here</A>.<P>
<HR>
<ADDRESS>Apache/1.3.34 Server at localhost Port 80</ADDRESS>
</BODY></HTML>
Connection to 62.133.206.90 closed by foreign host.
That doesn't mean the mirror is not working. In fact it is working.
You just have to use the correct Host: header.
Let me try to make myself clear. 1. I noticed a problem, where the
freshclam daemon process was gone, on three different systems, on two
geographically separate networks. 2. Investigating the problem, I
noticed the tail of the freshclam logfile, where it seems that freshclam
tried to connect to a first mirror, failed, then connected to a second
one and then nothing was logged anymore. 3. Then I tried to see what
would happen when I would run freshclam interactively. The result of
that session were included in my previous post: bash-2.05#
/opt/ClamAV/bin/freshclam ClamAV update process started at Fri Nov 3
12:13:42 2006 main.cvd is up to date (version: 40, sigs: 64138, f-level:
8, builder: tkojm) Can't connect to port 80 of host db.nl.clamav.net
(IP: 213.222.11.220) Trying host db.nl.clamav.net (62.133.206.90)...
Broken Pipe 4. AFAIK freshclam uses port 80 on the mirrors to get
updates. Hence, I tried to test connectivity by interactively telnetting
to port 80 on the two systems. Please note: I only wanted to test
connectivity. The first host showed a connection refused. The second
host accepted the connection, but dropped it. Now my method of testing
may not have been ideal for the situation. But I still have the question
what freshclam is doing when it can connect to a mirror, but it can't
fetch a complete, correct update? I'm afraid there's something wrong in
the error handling process for this situation. Before this weekend I
restarted all freshclam services. For one of them I configured to use
another mirror (db.DE.clamav.net). For the two others I kept
db.NL.clamav.net. The two freshclam servers which were still using
db.NL.clamav.net both exited during the weekend. Trace in the freshclam
logfile for the firss one: --------------------------------------
Received signal: wake up ClamAV update process started at Fri Nov 3
16:03:34 2006 main.cvd is up to date (version: 40, sigs: 64138, f-level:
8, builder: tkojm) daily.cvd is up to date (version: 2156, sigs: 11166,
f-level: 9, builder: ccordes) --------------------------------------
Received signal: wake up ClamAV update process started at Fri Nov 3
16:33:34 2006 main.cvd is up to date (version: 40, sigs: 64138, f-level:
8, builder: tkojm) (and then nothing, no more lines in the logfile, but
freshclam no longer runs). On the other host:
-------------------------------------- Received signal: wake up ClamAV
update process started at Sun Nov 5 18:40:45 2006 main.cvd is up to date
(version: 41, sigs: 73809, f-level: 10, builder: tkojm) WARNING: Your
ClamAV installation is OUTDATED! WARNING: Current functionality level =
9, recommended = 10 DON'T PANIC! Read http://www.clamav.net/faq.html
daily.cvd is up to date (version: 2162, sigs: 1601, f-level: 9, builder:
arnaud) -------------------------------------- Received signal: wake up
ClamAV update process started at Sun Nov 5 19:10:45 2006 main.cvd is up
to date (version: 41, sigs: 73809, f-level: 10, builder: tkojm) WARNING:
Your ClamAV installation is OUTDATED! WARNING: Current functionality
level = 9, recommended = 10 DON'T PANIC! Read
http://www.clamav.net/faq.html bash-2.05# (no more lines, and freshclam
gone).
Regarding this problem, I have the following questions:
4. Where do I report problems with mirrors?
To me,
Well, I see problems with the following two NL mirrors:
IP: 213.222.11.220, corresponding to clamav.packetstorm.nu, it is refusing
connections (and probably for quite some time now, I see on the stats page that
it is not reachable for more than 4.5 dayss).
And 62.133.206.90 gave the 'Broken Pipe' problem, and is at this very moment
not responding.
Regards
/rolf
Best regards
-- Luca Gibelli (luca _at_ clamav.net) - ClamAV, a GPL anti-virus
toolkit [Tel] +44 2081239239 [Fax] +39 0187015046 [IM]
nervous/jabber.linux.it PGP key id 5EFC5582 @ key server ||
http://www.clamav.net/gpg/luca.gpg
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
