Luca,
Thanks for the detailed answers. Only one of them doesn't ring true to me.
On 6/21/11 2:46 AM, "Luca Gibelli" <l...@clamav.net> wrote:
>
> Hello Al,
>
>> - 194.47.250.218 clamav.df.lth.se at this writing has been down for 17 days.
>
> this mirror is blocking our monitor tool but works just fine.
> In other words the status page shows it's down even if it's actually up.
>
I do two scheduled updates per day and rarely do a manual update at any
other time. My last successful update from this server was on May 3 at
15:45.
All attempts to use that server since then have been connection failures
with a success on the very next mirror tried. All errors logged were:
connect_error: getsockopt(SO_ERROR): fd=4 error=61: Connection refused
Can't connect to port 80 of host db.US.clamav.net (IP: 194.47.250.218)
May 9 15:45
May 10 15:45
May 11 7:45 & 15:45
May 12 7:45 & 15:45
May 15 7:45 & 15:45
May 16 7:45
& 15:45 Twice, 30 seconds apart?
May 17 7:45
May 18 7:45 & 15:45
May 19 7:45 & 15:45
May 23 7:45
Jun 2 7:45
Jun 5 7:45
Jun 10 15:45
Jun 12 7:45 & 15:45
Jun 15 15:45
So over a period of more than a month every attempt (23) to contact this
server failed in the same manner and there were only two errors involving
server 209.222.131.222 during the same period. I may be jumping to
conclusions, but I think it really was down for a very long time.
It also seems strange to me that the rotation scheme would pick this server
to go to first so many times in a row.
I don't routinely check the status of servers, but I started to after the
user I mentioned began complaining. He claims to have had even more
failures than I did. At any rate, while I watched, the bad days continued
to increase until last weekend. Looking at it right now it says it has been
up for three days straight and is only 1 hour behind, so it would seem that
your monitoring tool is no longer being blocked.
I see just now that it has worked it's way up to the top of my rr list, so I
expect I'll be seeing something from it soon.
-Al-
--
Al Varnell
Mountain View, CA
>> - 69.163.100.14 clamav.theshell.com was recently added back to the list of
>> US mirrors, has been down ever since, over 10 days and now see it has been
>> removed again.
>
> I removed it from the RR a long time ago. I'll remove it from the mirror
> status page after it's declared definitely dead.
>
>> - How many days does a mirror have to be old or bad before it is taken off
>> the list of available servers? Put another way, when should I start asking
>> about it?
>
> it's removed from the DNS RR usually after 10 days.
>
>> - Why are there so many (5) off-shore servers included in the list of
>> available US mirrors when there are around 11 in-country servers?
>
> because those 11 mirrors in US are not enough to handle all the traffic
> generated in US.
>
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
