Re: [clamav-users] Yet Another US Mirror Issue-Solved
On Sat, 17 Sep 2011 10:25:50 -0400 Dan dantear...@gmail.com wrote: 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? I've enabled short-time blacklisting of mirrors on connection errors in clamav-devel, please give it a try (use the git version): http://www.clamav.net/lang/en/download/sources/ Does that Ignore: Yes entry automatically expire at some point or is that mirror now dead forever? They will expire automatically. The mirrors ignored for a short time should return to the pool after 30 minutes (or 6 hours in clamav-devel after recent changes), and those ignored for a long term (due to severe or repeating issues) should get cleared after 3 days. Regards, -- oo. Tomasz Kojm tk...@clamav.net (\/)\. http://www.ClamAV.net/gpg/tkojm.gpg \..._ 0DCA5A08407D5288279DB43454822DC8985A444B //\ /\ Mon Sep 19 13:50:14 CEST 2011 ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [clamav-users] Yet Another US Mirror Issue-Solved
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
Re: [clamav-users] Yet Another US Mirror Issue-Solved
On Thu, 15 Sep 2011 12:38:40 -0700 Al Varnell alvarn...@mac.com wrote: [...] Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Database updated (1038850 signatures) from db.US.clamav.net (IP: 88.198.67.125) Database updated (1038850 signatures) from 88.198.67.125 (IP: 88.198.67.125) Database updated (1039253 signatures) from db.US.clamav.net (IP: 88.198.67.125) For all but 1 of the 21 of the Can't connects it immediately checked and connected and updated from another mirror, but the next update went right back to .125 in all but 2 cases. One Can't connect was followed by a second Can't connect. OK, so that's the expected behavior. -- oo. Tomasz Kojm tk...@clamav.net (\/)\. http://www.ClamAV.net/gpg/tkojm.gpg \..._ 0DCA5A08407D5288279DB43454822DC8985A444B //\ /\ Fri Sep 16 09:29:08 CEST 2011 ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [clamav-users] Yet Another US Mirror Issue-Solved
On Thu, 15 Sep 2011 12:28:27 -0400 Dan dantear...@gmail.com wrote: At 10:42 PM -0700 9/14/2011, Al Varnell wrote: Against all odds I've had three updates in the last 24 and two of them have been from old .125 Not so lucky; here every freshclam run that has touched .125 includes a failure still. My latest: ClamAV update process started at Thu Sep 15 12:16:56 2011 Using IPv6 aware code Querying current.cvd.clamav.net TTL: 900 Software version from DNS: 0.97.2 main.cvd version from DNS: 53 main.cvd is up to date (version: 53, sigs: 846214, f-level: 53, builder: sven) daily.cvd version from DNS: 13620 daily.cld is up to date (version: 13620, sigs: 193015, f-level: 60, builder: acab) safebrowsing.cvd version from DNS: 32299 Retrieving http://database.clamav.net/safebrowsing-32299.cdiff Ignoring mirror 65.19.179.67 (due to previous errors) nonblock_connect: connect timing out (30 secs) Can't connect to port 80 of host database.clamav.net (IP: 88.198.67.125) Ignoring mirror 65.19.179.67 (due to previous errors) Trying host database.clamav.net (207.57.106.31)... Trying to download http://database.clamav.net/safebrowsing-32299.cdiff (IP: 207.57.106.31) Downloading safebrowsing-32299.cdiff [100%] cdiff_apply: Parsed 56039 lines and executed 55991 commands Loading signatures from safebrowsing.cld Properly loaded 723320 signatures from new safebrowsing.cld safebrowsing.cld updated (version: 32299, sigs: 723320, f-level: 60, builder: google) Querying safebrowsing.32299.61.1.0.207.57.106.31.ping.clamav.net bytecode.cvd version from DNS: 144 bytecode.cld is up to date (version: 144, sigs: 41, f-level: 60, builder: edwin) Database updated (1762590 signatures) from database.clamav.net (IP: 207.57.106.31) This looks good, it properly switched to another mirror and successfully updated the database. -- oo. Tomasz Kojm tk...@clamav.net (\/)\. http://www.ClamAV.net/gpg/tkojm.gpg \..._ 0DCA5A08407D5288279DB43454822DC8985A444B //\ /\ Fri Sep 16 13:14:17 CEST 2011 ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [clamav-users] Yet Another US Mirror Issue-Solved
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. Regards, -- oo. Tomasz Kojm tk...@clamav.net (\/)\. http://www.ClamAV.net/gpg/tkojm.gpg \..._ 0DCA5A08407D5288279DB43454822DC8985A444B //\ /\ Fri Sep 16 13:23:52 CEST 2011 ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [clamav-users] Yet Another US Mirror Issue-Solved
On Wed, 14 Sep 2011 22:42:53 -0700 Al Varnell alvarn...@mac.com wrote: Against all odds I've had three updates in the last 24 and two of them have been from old .125, so I reserve the right to revisit the other part of the issue in a few days after I have some statistics on how often it gets used on the first attempt. Hey Al, please run 'freshclam -v' and look for this line: Using IPv6 aware code If it's not there, then most likely freshclam is using the older networking code, which does not randomize IP addresses on its own but only relies on the DNS. Regards, -- oo. Tomasz Kojm tk...@clamav.net (\/)\. http://www.ClamAV.net/gpg/tkojm.gpg \..._ 0DCA5A08407D5288279DB43454822DC8985A444B //\ /\ Thu Sep 15 10:17:13 CEST 2011 ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [clamav-users] Yet Another US Mirror Issue-Solved
On 9/15/11 1:30 AM, Tomasz Kojm tk...@clamav.net wrote: Hey Al, please run 'freshclam -v' and look for this line: Using IPv6 aware code If it's not there, then most likely freshclam is using the older networking code, which does not randomize IP addresses on its own but only relies on the DNS. Here it is: Current working dir is /usr/local/clamXav/share/clamav Max retries == 3 ClamAV update process started at Thu Sep 15 01:37:17 2011 Using IPv6 aware code Querying current.cvd.clamav.net TTL: 224 Software version from DNS: 0.97.2 main.cvd version from DNS: 53 main.cld is up to date (version: 53, sigs: 846214, f-level: 53, builder: sven) daily.cvd version from DNS: 13619 Retrieving http://db.US.clamav.net/daily-13618.cdiff Trying to download http://db.US.clamav.net/daily-13618.cdiff (IP: 207.57.106.31) Downloading daily-13618.cdiff [100%] cdiff_apply: Parsed 17 lines and executed 17 commands Retrieving http://db.US.clamav.net/daily-13619.cdiff Trying to download http://db.US.clamav.net/daily-13619.cdiff (IP: 207.57.106.31) Downloading daily-13619.cdiff [100%] cdiff_apply: Parsed 16 lines and executed 16 commands Loading signatures from daily.cld Properly loaded 193008 signatures from new daily.cld daily.cld updated (version: 13619, sigs: 193008, f-level: 60, builder: jesler) Querying daily.13619.62.1.0.207.57.106.31.ping.clamav.net bytecode.cvd version from DNS: 144 bytecode.cvd is up to date (version: 144, sigs: 41, f-level: 60, builder: edwin) Database updated (1039263 signatures) from db.US.clamav.net (IP: 207.57.106.31) Looks to be OK. -Al- -- Al Varnell Mountain View, CA ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [clamav-users] Yet Another US Mirror Issue-Solved
On Thu, 15 Sep 2011 01:41:29 -0700 Al Varnell alvarn...@mac.com wrote: Looks to be OK. OK, now please post the output of 'freshclam --list-mirrors' -- oo. Tomasz Kojm tk...@clamav.net (\/)\. http://www.ClamAV.net/gpg/tkojm.gpg \..._ 0DCA5A08407D5288279DB43454822DC8985A444B //\ /\ Thu Sep 15 10:41:30 CEST 2011 ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [clamav-users] Yet Another US Mirror Issue-Solved
On 9/15/11 1:43 AM, Tomasz Kojm tk...@clamav.net wrote: OK, now please post the output of 'freshclam --list-mirrors' Janets-iMac-G5:~ jvarnell$ sudo /usr/local/clamXav/bin/freshclam --list-mirrors Mirror #1 IP: 194.8.197.22 Successes: 12 Failures: 0 Last access: Tue Sep 13 15:45:14 2011 Ignore: No - Mirror #2 IP: 69.12.162.28 Successes: 4 Failures: 1 Last access: Thu Sep 8 07:45:14 2011 Ignore: No - Mirror #3 IP: 150.214.142.197 Successes: 6 Failures: 0 Last access: Wed Aug 24 07:45:08 2011 Ignore: No - Mirror #4 IP: 69.163.100.14 Successes: 13 Failures: 0 Last access: Tue Sep 13 19:40:16 2011 Ignore: No - Mirror #5 IP: 200.236.31.1 Successes: 8 Failures: 0 Last access: Thu Aug 25 15:45:11 2011 Ignore: No - Mirror #6 IP: 155.98.64.87 Successes: 14 Failures: 0 Last access: Wed Sep 7 15:45:09 2011 Ignore: No - Mirror #7 IP: 208.72.56.53 Successes: 7 Failures: 0 Last access: Sun Sep 11 07:45:04 2011 Ignore: No - Mirror #8 IP: 194.186.47.19 Successes: 6 Failures: 0 Last access: Fri Sep 9 15:45:19 2011 Ignore: No - Mirror #9 IP: 194.47.250.218 Successes: 31 Failures: 0 Last access: Sat Sep 10 15:47:31 2011 Ignore: No - Mirror #10 IP: 168.143.19.95 Successes: 13 Failures: 0 Last access: Mon Sep 5 07:45:07 2011 Ignore: No - Mirror #11 IP: 88.198.67.125 Successes: 10 Failures: 0 Last access: Wed Sep 14 15:46:40 2011 Ignore: No - Mirror #12 IP: 207.57.106.31 Successes: 6 Failures: 0 Last access: Thu Sep 15 01:37:23 2011 Ignore: No - Mirror #13 IP: 65.19.179.67 Successes: 8 Failures: 0 Last access: Sun Sep 11 15:47:38 2011 Ignore: No - Mirror #14 IP: 64.246.134.219 Successes: 8 Failures: 0 Last access: Tue Sep 13 07:45:07 2011 Ignore: No - Mirror #15 IP: 204.109.62.22 Successes: 5 Failures: 0 Last access: Thu Sep 8 15:45:17 2011 Ignore: No Note: Mirror #11 had Successes: 1 until yesterday. -Al- -- Al Varnell Mountain View, CA ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [clamav-users] Yet Another US Mirror Issue-Solved
On Thu, 15 Sep 2011 02:11:16 -0700 Al Varnell alvarn...@mac.com wrote: [...] - Mirror #11 IP: 88.198.67.125 Successes: 10 Failures: 0 Last access: Wed Sep 14 15:46:40 2011 Ignore: No - Mirror #12 IP: 207.57.106.31 Successes: 6 Failures: 0 Last access: Thu Sep 15 01:37:23 2011 Ignore: No - Mirror #13 IP: 65.19.179.67 Successes: 8 Failures: 0 Last access: Sun Sep 11 15:47:38 2011 Ignore: No - Mirror #14 IP: 64.246.134.219 Successes: 8 Failures: 0 Last access: Tue Sep 13 07:45:07 2011 Ignore: No - Mirror #15 IP: 204.109.62.22 Successes: 5 Failures: 0 Last access: Thu Sep 8 15:45:17 2011 Ignore: No Note: Mirror #11 had Successes: 1 until yesterday. And that's the reason freshclam was choosing it as the first mirror all the time. Freshclam tries to balance the load by preferring mirrors with the lowest number of downloads. Then, when it fails to connect to such a mirror, it should disable this load balancing and simply pick up a random mirror in the next attempt. Could you check your logs to see if that actually happened? -- oo. Tomasz Kojm tk...@clamav.net (\/)\. http://www.ClamAV.net/gpg/tkojm.gpg \..._ 0DCA5A08407D5288279DB43454822DC8985A444B //\ /\ Thu Sep 15 14:07:40 CEST 2011 ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [clamav-users] Yet Another US Mirror Issue-Solved
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? - 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
Re: [clamav-users] Yet Another US Mirror Issue-Solved
At 10:42 PM -0700 9/14/2011, Al Varnell wrote: Against all odds I've had three updates in the last 24 and two of them have been from old .125 Not so lucky; here every freshclam run that has touched .125 includes a failure still. My latest: ClamAV update process started at Thu Sep 15 12:16:56 2011 Using IPv6 aware code Querying current.cvd.clamav.net TTL: 900 Software version from DNS: 0.97.2 main.cvd version from DNS: 53 main.cvd is up to date (version: 53, sigs: 846214, f-level: 53, builder: sven) daily.cvd version from DNS: 13620 daily.cld is up to date (version: 13620, sigs: 193015, f-level: 60, builder: acab) safebrowsing.cvd version from DNS: 32299 Retrieving http://database.clamav.net/safebrowsing-32299.cdiff Ignoring mirror 65.19.179.67 (due to previous errors) nonblock_connect: connect timing out (30 secs) Can't connect to port 80 of host database.clamav.net (IP: 88.198.67.125) Ignoring mirror 65.19.179.67 (due to previous errors) Trying host database.clamav.net (207.57.106.31)... Trying to download http://database.clamav.net/safebrowsing-32299.cdiff (IP: 207.57.106.31) Downloading safebrowsing-32299.cdiff [100%] cdiff_apply: Parsed 56039 lines and executed 55991 commands Loading signatures from safebrowsing.cld Properly loaded 723320 signatures from new safebrowsing.cld safebrowsing.cld updated (version: 32299, sigs: 723320, f-level: 60, builder: google) Querying safebrowsing.32299.61.1.0.207.57.106.31.ping.clamav.net bytecode.cvd version from DNS: 144 bytecode.cld is up to date (version: 144, sigs: 41, f-level: 60, builder: edwin) Database updated (1762590 signatures) from database.clamav.net (IP: 207.57.106.31) - 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
Re: [clamav-users] Yet Another US Mirror Issue-Solved
On 9/15/11 5:19 AM, Tomasz Kojm tk...@clamav.net wrote: And that's the reason freshclam was choosing it as the first mirror all the time. Freshclam tries to balance the load by preferring mirrors with the lowest number of downloads. Then, when it fails to connect to such a mirror, it should disable this load balancing and simply pick up a random mirror in the next attempt. Could you check your logs to see if that actually happened? Here are the results of trying .125 over the same period, (Aug 29 to Sep 14). There were 42 attempted updates, 12 were already up-to-dates and 21 of 30 updates started with a 88.198.67.125 failure. Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host 88.198.67.125 (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Can't connect to port 80 of host db.US.clamav.net (IP: 88.198.67.125) Database updated (1038850 signatures) from db.US.clamav.net (IP: 88.198.67.125) Database updated (1038850 signatures) from 88.198.67.125 (IP: 88.198.67.125) Database updated (1039253 signatures) from db.US.clamav.net (IP: 88.198.67.125) For all but 1 of the 21 of the Can't connects it immediately checked and connected and updated from another mirror, but the next update went right back to .125 in all but 2 cases. One Can't connect was followed by a second Can't connect. -Al- -- Al Varnell Mountain View, CA ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
