Re: ClamAV consumes so much memory that my Postfix service gets killed by OOM Killer from time to time

Turritopsis Dohrnii Teo En Ming via clamav-users <[email protected]>
Newsgroups gmane.comp.security.virus.clamav.user
Message-ID <pYIZlleQYkkphl79l-YfFed1dCdw-FBgo9rdCgvykcrVE0pqqAIOg04p90n1Xss4XminXsxvkfdGAvlURGfDrAocdB2Kge_3_QbtHp-9_WU=@protonmail.com>
On Tuesday, March 4th, 2025 at 11:50 PM, Andrew C Aitchison <[email protected]> wrote:

> On Tue, 4 Mar 2025, Turritopsis Dohrnii Teo En Ming via clamav-users wrote:
> 
> > Good day from Singapore,
> > 
> > ClamAV consumes so much memory that my Postfix service gets killed
> > by OOM Killer from time to time.
> 
> 
> Yes, ClamAV needs 1-2GB RAM to store the database of malware to search for
> and double that when it loads an updated database (this doubling can be
> avoided but then ClamAV is unavailable while the update is loaded).
> 
> 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.
> 
> --
> Andrew C. Aitchison Kendal, UK
> [email protected]

I have sufficient physical memory. I have 8 GB of RAM in my VPS. I don't think I need to use swap/virtual memory.

Regards,

Mr. Turritopsis Dohrnii Teo En Ming
Targeted Individuals in Singapore
GIMP = Government-Induced Medical Problems
5th March 2025 Wednesday
_______________________________________________

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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.