On Tue, 13 Sep 2011 07:57:35 -0700 Al Varnell alvarn...@mac.com wrote:
On 9/12/11 6:59 PM, Dan dantear...@gmail.com wrote:
At 11:12 AM -0700 9/3/2011, Al Varnell wrote:
Both current.cvd.clamav.net and your home page say the latest version of
daily.cvd is 13538, but according to Twitter there
Yet more failure on 88.198.67.125, this morning. This one is a double.
Shouldn't Freshclam be smart enough to avoid the same failing server
at least within the same run?
ClamAV update process started at Tue Sep 13 10:45:01 2011
main.cvd is up to date (version: 53, sigs: 846214, f-level: 53,
On Sep 13, 2011, at 8:15 AM, Dan dantear...@gmail.com wrote:
Yet more failure on 88.198.67.125, this morning. This one is a double.
I was going to wait a few more days to mention this, but since you bring it
up...
I have seen this twice a day almost every day since 29 Aug. The only times I
Noone has suggested maximum. The issue is that the mirrors are so
overloaded that it's often taking freshclam an excessive amount of
time to do its thing, because of the time-outs / connection
failures. No big deal if it's the update run in the background. But
if it's on-demand update
Am 13.09.2011 18:01, schrieb Al Varnell:
On Sep 13, 2011, at 8:15 AM, Dan dantear...@gmail.com wrote:
Yet more failure on 88.198.67.125, this morning. This one is a double.
I was going to wait a few more days to mention this, but since you bring it
up...
I have seen this twice a day
On 9/13/2011 1:18 PM, sys...@ra-schaal.de wrote:
Am 13.09.2011 18:01, schrieb Al Varnell:
On Sep 13, 2011, at 8:15 AM, Dan dantear...@gmail.com wrote:
Yet more failure on 88.198.67.125, this morning. This one is a double.
I was going to wait a few more days to mention this, but since you
On 9/13/11 9:36 AM, Bryan Burke bbu...@eecs.utk.edu wrote:
Noone has suggested maximum. The issue is that the mirrors are so
overloaded that it's often taking freshclam an excessive amount of
time to do its thing, because of the time-outs / connection
failures. No big deal if it's the update
On 9/13/11 10:18 AM, sys...@ra-schaal.de sys...@ra-schaal.de wrote:
Am 13.09.2011 18:01, schrieb Al Varnell:
On Sep 13, 2011, at 8:15 AM, Dan dantear...@gmail.com wrote:
Yet more failure on 88.198.67.125, this morning. This one is a double.
I was going to wait a few more days to mention
I don't know the frequency, but it was enough of a problem for him to
complain...three times before I brought it up here.
So is this issue specifically with ClamXav? i.e. is ClamXav forcing an update
each time
it's run? I know that the regular clamav does not do this, and if that's the
Hi--
On Sep 13, 2011, at 12:49 PM, Bryan Burke wrote:
- Which always seems to be the first one checked
Actual issue. Perhaps DNS caching is a factor? If freshclam checks often
enough, then
perhaps the cache entry never dies, and you get the same order every time?
Running dig
On Sep 13, 2011, at 2:28 PM, Bryan Burke wrote:
...with zero successful connections to that IP. The connectivity failure is
entirely reproducible by hand:
% telnet 88.198.67.125 80
Trying 88.198.67.125...
telnet: connect to address 88.198.67.125: Connection refused
telnet: Unable to
On 9/13/2011 12:47 AM, Henrik K wrote:
If you are an individual not able to put $15-$100 a month, then yes, it's not
in your capability.
$15 - $100 extra / month would go to higher priority tasks / needs.
Some of our servers are nearly old enough to vote.
:-)
As an individual, or small
No, I get an immediate connection refused and an ICMP port unreachable back:
# tcpdump -nq host 88.198.67.125
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on en0, link-type EN10MB (Ethernet), capture size 65535 bytes
14:32:31.222347 IP
On 9/13/11 12:49 PM, Bryan Burke bbu...@eecs.utk.edu wrote:
I don't know the frequency, but it was enough of a problem for him to
complain...three times before I brought it up here.
So is this issue specifically with ClamXav? i.e. is ClamXav forcing an update
each time it's run?
No, the
On 9/13/11 2:28 PM, Bryan Burke bbu...@eecs.utk.edu wrote:
% grep Can't connect to port 80 of host database.clamav.net (IP:
88.198.67.125) /var/log/freshclam.log | wc -l
27
Interesting. When I just grep for the IP in my logs:
ib /var/log # grep 88.198.67.125 maillog* | wc -l
On 9/13/2011 7:07 PM, Al Varnell wrote:
On 9/13/11 2:28 PM, Bryan Burke bbu...@eecs.utk.edu wrote:
Since freshclam doesn't seem to log the IP (by default, at least) when the
update succeeds
(or there is no update), I have no good way of checking how many times
88.198.67.125 is queried.
My
My logs show successful update sources in the last line, but not when there
is no update.
Ok, well I did check the output of the grep before posting the number of lines
on this
list, and all log entries mentioning that IP were failures. So there's still
*technically*
some gray area, in that,
On 9/13/11 6:31 PM, Nathan Gibbs nat...@cmpublishers.com wrote:
On 9/13/2011 7:07 PM, Al Varnell wrote:
On 9/13/11 2:28 PM, Bryan Burke bbu...@eecs.utk.edu wrote:
Since freshclam doesn't seem to log the IP (by default, at least) when the
update succeeds
(or there is no update), I have no
Eliminate some unknowns - like maybe your DNS doesn't like big
packets. Add this *temporarily* to your host table:
88.198.67.125 db.us.big.clamav.net
And try again - and try with your browser, too. It should show you a
web page indentifying the site you connected to and then after a
On 9/13/2011 9:03 PM, Bryan Burke wrote:
My logs show successful update sources in the last line, but not when there
is no update.
Ok, well I did check the output of the grep before posting the number of
lines on this
list, and all log entries mentioning that IP were failures. So there's
On 9/13/11 7:53 PM, Noel Jones wrote:
On 9/13/2011 9:03 PM, Bryan Burke wrote:
My logs show successful update sources in the last line, but not when there
is no update.
Ok, well I did check the output of the grep before posting the number of lines
on this
list, and all log entries mentioning
On 9/13/11 8:05 PM, Dennis Peterson wrote:
I've just sent the URL to validator.wc3.org and got the same problem with this
message:
My fat fingers intended to type http://validator.wc.org and not what they did
type.
dp
___
Help us build a
On 9/13/11 6:58 PM, Dennis Peterson denni...@inetnw.com wrote:
On 9/13/11 3:15 PM, Bryan Burke wrote:
At least concerning this issue, is there anything more to be done?
Eliminate some unknowns - like maybe your DNS doesn't like big packets. Add
this
*temporarily* to your host table:
On 9/13/11 8:07 PM, Dennis Peterson denni...@inetnw.com wrote:
On 9/13/11 8:05 PM, Dennis Peterson wrote:
I've just sent the URL to validator.wc3.org and got the same problem with
this
message:
My fat fingers intended to type http://validator.wc.org and not what they did
type.
Or
On 9/13/11 8:31 PM, Al Varnell wrote:
Sounds like the server will be pulled, so you may not care, but since I went
through the effort.
Made changes to the hosts file.
Ran dig $ db.us.clamav.net
Does your dig use the host table? Mine does not. Same with nslookup. I can't
imagine why they
On 9/13/11 8:34 PM, Al Varnell wrote:
On 9/13/11 8:07 PM, Dennis Petersondenni...@inetnw.com wrote:
On 9/13/11 8:05 PM, Dennis Peterson wrote:
I've just sent the URL to validator.wc3.org and got the same problem with
this
message:
My fat fingers intended to type http://validator.wc.org
On 9/13/11 8:34 PM, Dennis Peterson denni...@inetnw.com wrote:
On 9/13/11 8:31 PM, Al Varnell wrote:
Sounds like the server will be pulled, so you may not care, but since I went
through the effort.
Made changes to the hosts file.
Ran dig $ db.us.clamav.net
Does your dig use the
On 09/13/2011 12:33 PM, Al Varnell wrote:
On 9/13/11 10:18 AM, sys...@ra-schaal.desys...@ra-schaal.de wrote:
Am 13.09.2011 18:01, schrieb Al Varnell:
On Sep 13, 2011, at 8:15 AM, Dandantear...@gmail.com wrote:
Yet more failure on 88.198.67.125, this morning. This one is a double.
I was
On 09/13/2011 01:16 PM, Chuck Swiger wrote:
This being said, there is definitely a recurring issue with this particular
mirror. Since Aug 22, I've seen:
% grep Can't connect to port 80 of host database.clamav.net (IP:
88.198.67.125) /var/log/freshclam.log | wc -l
27
...with zero
29 matches
Mail list logo
