Hi there,
On Tue, 19 Jul 2022, Emanuel Gonzalez wrote:
Hi, i use clamav in AWS ec2 instances c5.large. When I run the clamscan
command /home/user/testfile the cpu usage is triggered and the instance stops
responding.
Here my config:
clamd --version
ClamAV 0.103.6/26606/Tue Jul 19 04:57:30 2022
...
It would help if you were clearer about exactly what you are doing.
How much RAM do you have available? If you are using the 'official'
signature database you probably need at least 3, preferably 4 GBytes,
as loading ten million signatures will use about a gigabyte of RAM.
Loading ten million signatures takes a while. The 'clamd' daemon does
that when it starts and when the signatures are updated (about daily
for the 'official' signature database). The 'clamscan' utility does
it every time you run it. The 'clamdscan' utility never does it.
The 'clamdscan' utility uses 'clamd', but 'clamscan' does not.
Please show us the exact command which you use when the problem appears.
If you are running a clamd daemon *and* if you are really running
'clamscan' and not 'clamdscan' then you are probably using twice as
much memory as you need to - not to mention having to wait for the
clamscan process to read ten million signatures every time it runs.
--
73,
Ged.
_______________________________________________
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/Cisco-Talos/clamav-documentation
https://docs.clamav.net/#mailing-lists-and-chat
