On 3/18/19 7:02 PM, Micah Snyder (micasnyd) wrote:
Hi ellanios82,

How often do you update your signature database?  How often do you do a scan?
Did this slowdown just occur in the last few days, or last couple weeks?

I am curious if the slowdown occurred after daily-25380.cdiff (a database change that I 
am told removed many hash signatures from the database which would be detected by more 
efficient signatures), or if some change to bytecode signatures is causing much slower 
scans.  The message you reported "LibClamAV Warning: Bytecode 3 failed to run: Error 
during bytecode execution" isn't necessarily due to a bytecode timeout (which is 
more common), but indicates some sort of problem with a bytecode signature.  If you can 
identify what files cause this error, it would very helpful if we could analyze those 
files with the signature to see what is going wrong.

Thanks,
Micah


Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.

On 3/18/19, 3:52 AM, "clamav-users on behalf of ellanios82 via clamav-users" 
<clamav-users-boun...@lists.clamav.net on behalf of clamav-users@lists.clamav.net> wrote:
       - usually , i run ClamAV on my home PC once a week : have about 42 GB 
files in total
       - normally ClamAV takes about 4 hours to complete but , Today , ClamAV 
is running for 7 hours , and STILL not finished
       - something odd ??
p.s.
       Omitted to say, 7 times i receive this message :
     <LibClamAV Warning: Bytecode 3 failed to run: Error during bytecode 
execution>
...... - Eventually finished : took 12 Hours to scan 44 GB [ normally, would have expected 4 Hours to scan my 44 GB ]

       thanks
     ........


...

 Hi Micah ,


 - i scan once a week : before scan ,  do 'update my signature database'


......

 regards



_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
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

Reply via email to