>From my local validation with ClamAV, I can confidently say that
safebrowsing CVD 48474 will load much faster than safebrowsing CVD 48473.
It's all in the ordering. We'll be keeping track of that going forward.
Safebrowsing 48474 is available from the mirror network now.
Dave R.
On Wed, Mar 6,
Hi Dave,
I noticed that the safebrowsing CVD was updated (I'm seeing version 48474
now) but the cdiff takes a VERY long time to apply and the new gdb file
takes about the same time to load.
Freshclam hangs at this point:
Wed Mar 6 16:03:05 2019 -> *Retrieving
ment
> > Talos
> > Cisco Systems, Inc.
> >
> >
> > From: clamav-users on behalf
> > of Paul via clamav-users Reply-To:
> > ClamAV users ML Date: Wednesday,
> > March 6, 2019 at 7:30 AM To: "clamav-users@lists.clamav.net"
> > Cc: Pa
gt;
>
> From: clamav-users on behalf
> of Paul via clamav-users Reply-To:
> ClamAV users ML Date: Wednesday,
> March 6, 2019 at 7:30 AM To: "clamav-users@lists.clamav.net"
> Cc: Paul
> Subject: Re: [clamav-users] Problem with freshclam updating
> daily-25380.cdiff
&
Maarten,
Thanks for reporting that. There is an ordering difference of the content
in the latest GDB file which is affecting the load time, and we will be
fixing that in the next safebrowsing CVD version.
Dave R.
On Wed, Mar 6, 2019 at 10:42 AM Maarten Broekman via clamav-users <
I'm not sure if the safebrowsing.cld is included in the daily cdiff, but
the current safebrowsing.cld takes between 50 and 70 seconds to *load* into
clamscan, where a copy from February loads in <5 seconds.
safebrowsing data:
Old (fast): ClamAV-VDB:13 Feb 2019 13-16
I confirmed with our signature management team that the extended time
processing daily-25380 is because this change is significantly larger than a
standard update.
This update drops 768053 hash-based signatures for malware that is detected by
other more efficient logical signatures. The net
On Wed, 2019-03-06 at 14:20 +, Micah Snyder (micasnyd) via clamav-
users wrote:
> Pierre,
>
> So you're saying it actually did finish after 3 hours, 15 minutes on
> its own? That is good news for all of the automated systems, even if
> this is a potentially terrible bug.
>
> I'm still
Yes Micah, it finished while I was checking the computer because of the
messages received
on the mailing list.
$ tail -50 /var/log/freshclam.log
...
--
ClamAV update process started at Wed Mar 6 11:37:46 2019
WARNING: Your ClamAV installation is OUTDATED!
Pierre,
So you're saying it actually did finish after 3 hours, 15 minutes on its own?
That is good news for all of the automated systems, even if this is a
potentially terrible bug.
I'm still investigating the cause, and asking our signature management team if
they have any additional
Seems like this has been fixed.
Remove /var/lib/clamav/daily.* (either cld or cvd) and run freshclam again.
When freshclam failed to update, it was stuck on a .cld file. After removing
it, it downloaded daily.cvd and could be updated afterwards.
Dennis Hermannsen
System administrator |
: clamav-users on behalf of Paul
via clamav-users
Reply-To: ClamAV users ML
Date: Wednesday, March 6, 2019 at 7:30 AM
To: "clamav-users@lists.clamav.net"
Cc: Paul
Subject: Re: [clamav-users] Problem with freshclam updating daily-25380.cdiff
Same here ..
On 06/03/2019 11:31, Vijayak
Here too: it took about 3 hours and 15 minutes to calm down (SPARC, Solaris 11,
v0.100.0)... without noticiable error in freshclam.log.
On 6 Mar 2019 at 6:27, J.R. via clamav-users wrote:
> When crontab execs freshclam
> CPU server goes to 100%
> Hanged finishing Downloading daily-25380.cdiff
Same here ..
On 06/03/2019 11:31, Vijayakumar U via clamav-users wrote:
Yes. Same here too...
On Wed, 6 Mar 2019 at 16:24, Carlos García Gómez
mailto:carlos.gar...@f-integra.org>> wrote:
Hello,
When crontab execs freshclam
CPU server goes to 100%
Hanged finishing
> When crontab execs freshclam
> CPU server goes to 100%
> Hanged finishing Downloading daily-25380.cdiff [100%]
Just checked my server and it happened to me too! A little after 5am
central time. :(
___
clamav-users mailing list
Yes. Same here too...
On Wed, 6 Mar 2019 at 16:24, Carlos García Gómez <
carlos.gar...@f-integra.org> wrote:
> Hello,
>
> When crontab execs freshclam
> CPU server goes to 100%
> Hanged finishing Downloading daily-25380.cdiff [100%]
>
>
>
> /home/vmail/antivirus/clamav/bin/freshclam -v --debug
>
Hello,
When crontab execs freshclam
CPU server goes to 100%
Hanged finishing Downloading daily-25380.cdiff [100%]
/home/vmail/antivirus/clamav/bin/freshclam -v --debug
Current working dir is /home/vmail/antivirus/clamav-0.101.1/share/clamav
ClamAV update process started at Wed Mar 6
17 matches
Mail list logo
