On Tue, 4 Mar 2025, Turritopsis Dohrnii Teo En Ming via clamav-users wrote:
ClamAV consumes so much memory that my Postfix service gets killed
by OOM Killer from time to time.
On 04.03.25 15:52, Andrew C Aitchison via clamav-users wrote:
Yes, ClamAV needs 1-2GB RAM to store the database of malware to search for
this applies to "clamd" and every "clamscan" instance.
OP mentioned using clamscan.
BTW it's usually about 1.5GB with standard databases.
and double that when it loads an updated database (this doubling can be
avoided but then ClamAV is unavailable while the update is loaded).
This applies to "clamd". But even in case of DB reloading it's less than 3
clamscan instances.
I've had problems reloading 32-bit clamav when I loaded hude 3rd party DB.
The database of malware could be trimmed by looking for fewer viruses etc.
but I think that would be above your skill level, and it would increase
the chance of something nasty getting past your defences.
You could try increasing the size of the swap file/partition;
this could make the machine slower some of the time, but might make
the OOM Killer less likely to kick in.
The solution was already proposed: using clamd and clamsdcan.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
He who laughs last thinks slowest.
_______________________________________________
Manage your clamav-users mailing list subscription / unsubscribe:
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
