[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
On Tuesday, March 4th, 2025 at 12:13 AM, Dimitris T. via Postfix-users wrote: > Στις 3/3/25 17:32, ο/η Turritopsis Dohrnii Teo En Ming via Postfix-users > έγραψε: > > > Noted Patrick. I will ask Virtualmin developers to use clamd instead of > > clamdscan and clamscan. > > > > On Monday, March

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Dimitris T. via Postfix-users
Στις 3/3/25 17:32, ο/η Turritopsis Dohrnii Teo En Ming via Postfix-users έγραψε: Noted Patrick. I will ask Virtualmin developers to use clamd instead of clamdscan and clamscan. On Monday, March 3rd, 2025 at 11:25 PM, Patrick Ben Koetter via Postfix-users wrote: * Turritopsis Dohrnii Teo

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
Yes. On Monday, March 3rd, 2025 at 11:25 PM, Markus Schönhaber via Postfix-users wrote: > 03.03.25, 16:08 +0100, Turritopsis Dohrnii Teo En Ming via Postfix-users: > > > I have no control over whether clamdscan or clamscan is being run. > > Virtualmin developers determine that.Everything insid

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
On Monday, March 3rd, 2025 at 11:31 PM, Matus UHLAR - fantomas via Postfix-users wrote: > > * Turritopsis Dohrnii Teo En Ming via Postfix-users > > teo.en.m...@protonmail.com: > > > > > Dear Patrick Ben Koetter, > > > > > > I will suggest Virtualmin developers to use clamdscan instead

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Matus UHLAR - fantomas via Postfix-users
* Turritopsis Dohrnii Teo En Ming via Postfix-users : Dear Patrick Ben Koetter, I will suggest Virtualmin developers to use clamdscan instead of clamscan. Looks like a re-design of Virtualmin in how it uses ClamAV to scan email messages is required. On 03.03.25 16:25, Patrick Ben Koetter vi

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
Noted Patrick. I will ask Virtualmin developers to use clamd instead of clamdscan and clamscan. Thank you. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individuals in Singapore GIMP = Government-Induced Medical Problems 3rd March 2025 Monday On Monday, March 3rd, 2025 at 11:25 PM,

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
Lol I don't understand. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individuals in Singapore On Monday, March 3rd, 2025 at 11:30 PM, Matus UHLAR - fantomas via Postfix-users wrote: > > On Monday, March 3rd, 2025 at 10:17 PM, Wietse Venema via Postfix-users > > postfix-users@po

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Matus UHLAR - fantomas via Postfix-users
On Monday, March 3rd, 2025 at 10:17 PM, Wietse Venema via Postfix-users wrote: Turritopsis Dohrnii Teo En Ming via Postfix-users: > top - 20:56:04 up 2 days, 4:01, 1 user, load average: 3.38, 3.50, 3.89 > Tasks: 218 total, 6 running, 212 sleeping, 0 stopped, 0 zombie > %Cpu(s): 49.6 us, 5.9 s

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Markus Schönhaber via Postfix-users
03.03.25, 16:08 +0100, Turritopsis Dohrnii Teo En Ming via Postfix-users: > I have no control over whether clamdscan or clamscan is being run. > Virtualmin developers determine that.Everything inside Virtualmin > is packaged nicely. I didn't have to make any decisions. Then it's completely obviou

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Patrick Ben Koetter via Postfix-users
* Turritopsis Dohrnii Teo En Ming via Postfix-users : > Dear Patrick Ben Koetter, > > I will suggest Virtualmin developers to use clamdscan instead of clamscan. > Looks like a re-design of Virtualmin in how it uses ClamAV to scan email > messages is required. Don't do that. Ask them to use cla

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
Dear Patrick Ben Koetter, Yes, I will do that. Thank you. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individuals in Singapore GIMP = Government-Induced Medical Problems 3rd March 2025 Monday On Monday, March 3rd, 2025 at 11:09 PM, Patrick Ben Koetter via Postfix-users wrote:

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
Dear Patrick Ben Koetter, I will suggest Virtualmin developers to use clamdscan instead of clamscan. Looks like a re-design of Virtualmin in how it uses ClamAV to scan email messages is required. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individuals in Singapore GIMP = Government-I

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
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 wrote: > Hello, > > theory: > > you use > > postfix > amavisd-new > clamav > > You scan incoming (and outgoing) ema

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Patrick Ben Koetter via Postfix-users
* Turritopsis Dohrnii Teo En Ming via Postfix-users : > I have no idea which one to use. I only know that ClamAV is integrated into > Virtualmin. Everything is automatic. Talk you the vendor who provided the integration and ask them to provide a useful solution. p@rick -- [*] sys4 AG https:/

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
I have no control over whether clamdscan or clamscan is being run. Virtualmin developers determine that. Everything inside Virtualmin is packaged nicely. I didn't have to make any decisions. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individuals in Singapore GIMP = Government-Induced

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
I have no idea which one to use. I only know that ClamAV is integrated into Virtualmin. Everything is automatic. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individuals in Singapore GIMP = Government-Induced Medical Problems 3rd March 2025 Monday On Monday, March 3rd, 2025 at 10:

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Patrick Ben Koetter via Postfix-users
* Mark via Postfix-users : > Disable clamav completely, restart your server and try it like that, > for a few days. Nope! I don't see any reason to disable ClamAV completely. What I would definitely would to is *not* use the command line scanner utility clamscan to scan messages for malware. This

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Florian Piekert via Postfix-users
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 em

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
Dear Mark, ClamAV is fully integrated into my Virtualmin web hosting control panel. I do not know how to disable ClamAV completely. Please advise. Thank you. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individuals in Singapore GIMP = Government-Induced Medical Problems 3rd March 2025

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Gary R. Schmidt via Postfix-users
Do you know why my ClamAV is consuming so much memory? A more pertinent question is why aren't you using clamdscan? It only uses large amounts of memory on system start-up and when it reloads the AV data. Where clamscan uses that much memory every time it starts. Cheers,

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Varadi Gabor via Postfix-users
2025. 03. 03. 15:38 keltezéssel, Turritopsis Dohrnii Teo En Ming via Postfix-users írta: Do you know why my ClamAV is consuming so much memory? It stores samples there for virus identification. You need to use a clamav-daemon and clamdscan for scans instead of plain clamscan -- [Varadi G

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
On Monday, March 3rd, 2025 at 10:17 PM, Wietse Venema via Postfix-users wrote: > Turritopsis Dohrnii Teo En Ming via Postfix-users: > > > top - 20:56:04 up 2 days, 4:01, 1 user, load average: 3.38, 3.50, 3.89 > > Tasks: 218 total, 6 running, 212 sleeping, 0 stopped, 0 zombie > > %Cpu(s): 49.6 u

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
Sent with Proton Mail secure email. On Monday, March 3rd, 2025 at 10:17 PM, Florian Piekert via Postfix-users 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-use

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Mark via Postfix-users
Disable clamav completely, restart your server and try it like that, for a few days. ClamAV is a RAM killer! On Mon, Mar 3, 2025 at 5:34 PM Turritopsis Dohrnii Teo En Ming via Postfix-users wrote: > > Dear Varadi Gabor, > > I have just asked ChatGPT Artificial Intelligence (AI) for assistance. >

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
Dear Varadi Gabor, I have just asked ChatGPT Artificial Intelligence (AI) for assistance. ChatGPT says: To find out which process was killed by the OOM (Out-of-Memory) Killer in Linux, you can check the system logs. Here are some methods: <---snipped---> [root@ns1 ~]# dmesg | grep -i 'oom'

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Wietse Venema via Postfix-users
Turritopsis Dohrnii Teo En Ming via Postfix-users: > top - 20:56:04 up 2 days, 4:01, 1 user, load average: 3.38, 3.50, 3.89 > Tasks: 218 total, 6 running, 212 sleeping, 0 stopped, 0 zombie > %Cpu(s): 49.6 us, 5.9 sy, 0.0 ni, 0.0 id, 5.9 wa, 0.0 hi, 0.0 si, 38.7 > st > MiB Mem : 76

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Florian Piekert via Postfix-users
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

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Varadi Gabor via Postfix-users
2025. 03. 03. 14:55 keltezéssel, Turritopsis Dohrnii Teo En Ming via Postfix-users írta: [root@ns1 ~]# ps -efl | grep postfix 5 S root 517304 1 0 80 0 - 9542 ep_pol 19:32 ?00:00:01 /usr/libexec/postfix/master -w 4 S postfix 517306 517304 0 80 0 - 11770 ep_pol 19:

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread 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

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Varadi Gabor via Postfix-users
2025. 03. 03. 14:50 keltezéssel, Turritopsis Dohrnii Teo En Ming via Postfix-users írta: Hi, I didn't post everything in the output. I understand that, but that's where you could see what's running and what might not fit. -- [Varadi Gabor] ___

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
On Monday, March 3rd, 2025 at 9:49 PM, Gary R. Schmidt via Postfix-users wrote: > On 4/3/25 00:04, Turritopsis Dohrnii Teo En Ming via Postfix-users wrote: > > > Dear Wietse Venema, > > > > The output of LINUX command "systemctl status postfix" already shows > > postfix service alone was usin

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
On Monday, March 3rd, 2025 at 9:46 PM, Varadi Gabor via Postfix-users wrote: > 2025. 03. 03. 14:04 keltezéssel, Turritopsis Dohrnii Teo En Ming via > Postfix-users írta: > > > Dear Wietse Venema, > > > > The output of LINUX command "systemctl status postfix" already shows > > postfix service

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Gary R. Schmidt via Postfix-users
On 4/3/25 00:04, Turritopsis Dohrnii Teo En Ming via Postfix-users wrote: Dear Wietse Venema, The output of LINUX command "systemctl status postfix" already shows postfix service alone was using 6.2 GB of RAM. [root@ns1 ~]# top top - 20:56:04 up 2 days, 4:01, 1 user, load average: 3.38, 3.5

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Varadi Gabor via Postfix-users
2025. 03. 03. 14:04 keltezéssel, Turritopsis Dohrnii Teo En Ming via Postfix-users írta: Dear Wietse Venema, The output of LINUX command "systemctl status postfix" already shows postfix service alone was using 6.2 GB of RAM. [root@ns1 ~]# top top - 20:56:04 up 2 days, 4:01, 1 user, load ave

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
Dear Varadi Gabor, It is AlmaLinux 9.5. https://forum.virtualmin.com/t/i-have-found-out-the-reason-why-postfix-keeps-getting-killed-by-oom-killer/132370 Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individuals in Singapore GIMP = Government-Induced Medical Problems 3rd March 2025 Monda

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Varadi Gabor via Postfix-users
2025. 03. 02. 14:50 keltezéssel, Turritopsis Dohrnii Teo En Ming via Postfix-users írta: Then I tried rebooting my Virtual Private Server (VPS) in Germany but it did not solve the problem. What distribution and what version of it is running on the VPS? -- [Varadi Gabor] __

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
[root@ns1 ~]# systemctl status ● ns1..com State: degraded Units: 273 loaded (incl. loaded aliases) Jobs: 0 queued Failed: 1 units Since: Sun 2025-03-02 00:54:32 +08; 1 day 20h ago systemd: 252-46.el9_5.2.alma.1 Tainted: local-hwclock [root@ns1 ~]# systemctl --failed UNIT

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
Dear Wietse Venema, The output of LINUX command "systemctl status postfix" already shows postfix service alone was using 6.2 GB of RAM. [root@ns1 ~]# top top - 20:56:04 up 2 days, 4:01, 1 user, load average: 3.38, 3.50, 3.89 Tasks: 218 total, 6 running, 212 sleeping, 0 stopped, 0 zombie

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
Good day from Singapore, [root@ns1 ~]# postconf -nf alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases allow_percent_hack = no broken_sasl_auth_clients = yes command_directory = /usr/sbin compatibility_level = 2 daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postf

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Wietse Venema via Postfix-users
Turritopsis Dohrnii Teo En Ming via Postfix-users: > Dear Wietse Venema, > > Please refer to the output of Linux command "systemctl status postfix". > > [CODE] > > postfix.service - Postfix Mail Transport Agent > Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; > preset: d

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-03 Thread Turritopsis Dohrnii Teo En Ming via Postfix-users
Dear Wietse Venema, Please refer to the output of Linux command "systemctl status postfix". [CODE] postfix.service - Postfix Mail Transport Agent Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; preset: disabled) Active: active (running) since Sat 2025-03-01 16:30:47

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-02 Thread Viktor Dukhovni via Postfix-users
On Sun, Mar 02, 2025 at 10:08:04AM -0500, Wietse Venema via Postfix-users wrote: > This sounds like a bad builds, bad install, or bad hardware. My > primary MX host has 2GB of memory and it never runs out. > > If the problem happens again, can you find out WHAT PROGRAM is > consuming virtual memor

[pfx] Re: I have found out the reason why Postfix keeps getting killed by OOM Killer

2025-03-02 Thread Wietse Venema via Postfix-users
This sounds like a bad builds, bad install, or bad hardware. My primary MX host has 2GB of memory and it never runs out. If the problem happens again, can you find out WHAT PROGRAM is consuming virtual memory? Use top, ps, or whatever tool you are comfortable with. It's no good to give one nimber