[Pkg-clamav-devel] Bug#743305: clamav-freshclam: Stops downloading updates (daily.cvd) from local mirror

[Andreas Cadhalpun]

Hi,

On 03.04.2014 11:38, Simon Hobson wrote:
> Overnight I left Freshclam stopped on the master, so by this morning it was 3 revisions behind.
>
> Using PrivateMirror, one slave correctly recovered once the master was updated.

So it apparently works correct now. :)

> However, there is a logging/feedback issue with PrivateMirror. The slave was sat there reporting that :
>> daily.cvd is up to date (version: 18732 ...
> This is correct in as much as the PrivateMirror had version 18732, but incorrect in that the current version at the time was 18735. Nagios correctly picked up the fact that it was 3 revisions behind.

I think this is a feature not a bug. If you use a PrivateMirror, you can 
use completely different versions.

> Also, the logging is a bit verbose with warnings (as reported with Logwatch) :
>> Last Status:
>>      Reading CVD header (main.cld): WARNING: main.cld not found on remote server
>>      Reading CVD header (main.cvd): OK
>>      main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
>>      Reading CVD header (daily.cld): WARNING: daily.cld not found on remote server
>>      Reading CVD header (daily.cvd): OK
>>      daily.cvd is up to date (version: 18732, sigs: 865515, f-level: 63, builder: neo)
>>      Reading CVD header (bytecode.cld): WARNING: bytecode.cld not found on remote server
>>      Reading CVD header (bytecode.cvd): OK
>>      bytecode.cvd is up to date (version: 236, sigs: 43, f-level: 63, builder: dgoddard)
> While before it just logged :
>> Last Status:
>>      main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
>>      daily.cvd is up to date (version: 18716, sigs: 860736, f-level: 63, builder: neo)
>>      bytecode.cvd is up to date (version: 236, sigs: 43, f-level: 63, builder: dgoddard)

You followed my advice and used 'PrivateMirror <ip-address>'?
Try with 'PrivateMirror <DNS-name>'. From a quick look at the code, this 
might remove the additional messages.

> Thanks for the offer of a build with the patch. I'm happy to test it if it helps.

As it works now, I don't think this will be necessary.

Best regards,
Andreas