At 1:33 PM +0200 9/16/2011, Tomasz Kojm wrote:
On Thu, 15 Sep 2011 12:28:50 -0400 Dan <dantear...@gmail.com> wrote:
> At 10:43 AM +0200 9/15/2011, Tomasz Kojm wrote:
>> OK, now please post the output of 'freshclam --list-mirrors'
>
> Mirror #9
IP: 88.198.67.125
Successes: 13
Failures: 0
Last access: Fri Aug 26 10:45:31 2011
Ignore: No
-------------------------------------
Mirror #10
> IP: 65.19.179.67
Successes: 24
Failures: 5
Last access: Tue Sep 13 10:45:48 2011
Ignore: Yes
>
"Can't connect to port 80 of host database.clamav.net (IP:
88.198.67.125)" is not considered a failure? Is there something that I
can add to freshclam.conf to make it so?
A connection problem was considered a failure in the past but it was
making more harm than good. In most cases the problem lies at the
user's end (keep in mind we have ~2M different IPs downloading the
database every day) and according to our tests and user reports with
the current settings freshclam can more effectively deal with
network errors.
So... there is nothing that an end-user can set that will make the
connection error be considered a failure? I would need to go hack at
the source code?
Does that "Ignore: Yes" entry automatically expire at some point or
is that mirror now dead forever?
I see that all but one of the mirrors marked as "Ignore: Yes" work
fine (well, at least they respond to http://ip, which .125 does not).
Is there a command I can throw at Clam that will reset that flag?
Doesn't look like mirrors.dat is directly editable.
How many connection failures are required before a mirror is taken
out of rotation?
Thu Sep 15 22:05:35 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Fri Sep 16 08:03:05 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Fri Sep 16 10:03:06 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Fri Sep 16 11:03:08 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Fri Sep 16 14:03:09 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Fri Sep 16 14:42:04 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Fri Sep 16 16:03:09 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Fri Sep 16 17:03:07 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Fri Sep 16 18:03:07 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Fri Sep 16 19:03:09 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Fri Sep 16 20:03:09 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Fri Sep 16 21:03:06 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Fri Sep 16 22:03:06 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Sat Sep 17 01:03:06 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Sat Sep 17 02:03:09 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Sat Sep 17 03:03:09 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Sat Sep 17 04:03:09 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Sat Sep 17 05:03:08 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Sat Sep 17 06:03:08 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Sat Sep 17 07:03:08 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Sat Sep 17 08:03:06 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
Sat Sep 17 10:03:07 2011 -> Can't connect to port 80 of host
db.US.clamav.net (IP: 88.198.67.125)
That's a total of 0 successes over the past few days for that mirror.
Thanks,
- Dan.
--
- Psychoceramic Emeritus; South Jersey, USA, Earth.
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
