On 1/7/13 11:29 PM, "[email protected]" wrote: > Am 08.01.2013 07:40, schrieb Al Varnell: >> I feel confident that it is not that the diffs haven't made it out to the >> mirrors yet, but that they are no longer there because the mirrors only >> retain diffs for a given amount of time. > > I just found 75 diffs for daily.cvd on my mirror. This should be enough > but it should be no problem for the mirror-cordinators to increase the > number of files. > 75, thanks, that's what I needed to know. That number used to last a couple of weeks when there were only a half dozen diffs a day, but now it's considerably less than that.
>> The only occurrence when I saw >> this on my machine was after it had been down for five days over the >> Christmas holiday. In my case I do two updates a day and my network >> reliability is very good, so at most I only need to download about twenty >> diff files. The users that have been experiencing this have needed 80 to >> 100 diffs to become current. Part of the reason is the holidays and at >> least one seems to be experiencing network issues that complicate his setup. > > This may be a reason but there seems something more not working as > expected. According to your hint due to the limited diffs, i checked my > logs for 404-errors. And i found a lot! > > Usually freshclam should get the latest .cvd if some diffs are missing > on the server. But i found something like: > > GET /daily-16436.cdiff HTTP/1.0" 200 > GET /daily-13811.cdiff HTTP/1.0" 404 > > The second connect was made 8 hours after the first one. Both were > comming from the same ip and regarding to the user-agent it was the same > user. I see no reason to download 13811 when 16436 is allready downloaded. > I agree, but none of the examples I have show that to be happening here. They were all looking for the next one needed and failing if it had already been purged. > I think, it`s more a dns-problem (freshclam checks for updates by dns) > than anything else. A few months ago i had some trouble when checking > the current version of clamav by dns. > I see a few DNS failures, but they tend to be the ISP's fault. Switching to a public DNS usually fixes things. -Al- -- Al Varnell Mountain View, CA _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
