Dear Florian, Noted with thanks.
Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individuals in Singapore On Monday, March 3rd, 2025 at 10:54 PM, Florian Piekert <flo...@floppy.org> wrote: > Hello, > > theory: > > you use > > postfix > amavisd-new > clamav > > You scan incoming (and outgoing) emails with amavis and clam. > > When new clam signatures get installed, the freshclam process informs clamd > to reload these. That process can take some while. > > In the meantime postfix asks amavis to scan a new email. Clamd does not > respond (since it still loads the new signatures) and the request times out. > Then as a fallback clamscan is used, loading the signatures, taking some > time, and so on. > > WHY the amount of memory is high I do not know, maybe while loading the > signatures and to internally process those. > > Problem is, the loading takes a lot of I/O from the "physical" disk, a VPS is > slow with that usually. So it escalates it further and further. > > Solution: ensure to only have 1 instance of clamd running (and not 2 as you > currently maybe have) and maybe try to get a better I/O performance of your > VPS > or > LESS signatures for clamd. > > As written, only guesses based on assumptions. > > Florian > > > Sent with Proton Mail secure email. > > > > On Monday, March 3rd, 2025 at 10:17 PM, Florian Piekert via Postfix-users > > postfix-users@postfix.org wrote: > > > > > Hello all, > > > > > > Am 03.03.2025 um 15:09 schrieb Varadi Gabor via Postfix-users: > > > > > > > 2025. 03. 02. 14:50 keltezéssel, Turritopsis Dohrnii Teo En Ming via > > > > Postfix-users írta: > > > > > > > > > But until now I still have no idea why 115 messages stuck in the mail > > > > > queue will cause postfix to consume ENORMOUS amounts of RAM and cause > > > > > it to get killed by the OOM Killer. OOM = Out of Memory. > > > > > > > > In the syslog or whatever it is, isn't it in the OOM KILLER section > > > > what exactly killed it? > > > > > > > > -- process name, > > > > -- pid, > > > > -- memory allocation, etc. > > > > > > I remember an earlier message here, including information about the > > > clamav/clamd/clamscan processes, those had > 2.4GB memory already > > > allocated and were running concurrently. Maybe that's a source to look > > > at, too? > > > > > > Florian > > > > Do you know why my ClamAV is consuming so much memory? > > _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
