Hi Mark, I think I know what happened on your system. The CDN (cloudflare) sometimes sends cached responses for daily.cvd downloads, and presumably also does for main.cvd. If you got a cached main.cvd version 59 after attempting to download version 60, then it would try a new download all over again the next time you run freshclam.
We just cleared the cache on cloudflare so hopefully this doesn't happen again. Clearing the cache hasn't been reliable, in my experience, so if we get more reports of this we'll clear it again. Meanwhile, we're building a minor patch version for main.cvd and publish version 61. Combine that with the daily update for daily.cvd and we should be back to normal tomorrow morning. Regards, Micah > -----Original Message----- > From: clamav-users <[email protected]> On Behalf Of > Mark E. Mallett > Sent: Wednesday, July 14, 2021 5:51 PM > To: ClamAV users ML <[email protected]> > Subject: Re: [clamav-users] Freshclam updates problem > > On Wed, Jul 14, 2021 at 11:55:06PM +0000, Micah Snyder (micasnyd) via > clamav-users wrote: > > ... > > > > But it seems 0.103 has a second bug where it will patiently wait > > until it's at least 2 versions behind before it downloads the whole > > CVD database. This behavior is supposed to happen when a private > > mirror doesn't have the latest patch file yet, but wasn't supposed to > > happen for a zero-byte patch file. So we clearly have 2 bugs to fix ASAP. > > FWIW: 0.103.0 here; freshclam does say we're 1 diff behind. It fails to apply > the > diff with the seek error mentioned: > > ERROR: cdiff_apply: lseek(desc, -350, SEEK_END) failed > ERROR: downloadPatch: Can't apply patch > > But then it *does* download the two new .cvd files. Or at least two new .cvd > files, I can't tell if they are the latest but I assume so. > Next time around, the process repeats and we do the big downloads again. > > This may be what you meant but it doesn't sound like it. Just thought I'd pipe > up. > > -mm- > > PS when I first saw the daemon reports I tried clearing the data and running > freshclam by hand. Since it downloaded the two new .cvd files I assumed it had > self-corrected, so I did the same on all servers. > I was surprised on next daemon run to see the errors again, and tried a manual > run again and got the same errors. > > I figured the problem was related to the new thing today; I was going to stop > all freshclams until I looked deeper or heard more. But it sounds like > wait-and- > see for now. > > _______________________________________________ > > clamav-users mailing list > [email protected] > https://lists.clamav.net/mailman/listinfo/clamav-users > > > Help us build a comprehensive ClamAV guide: > https://github.com/vrtadmin/clamav-faq > > http://www.clamav.net/contact.html#ml _______________________________________________ clamav-users mailing list [email protected] https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
