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 +08; 1min 58s ago
Process: 697 ExecStartPre=/usr/sbin/restorecon -R /var/spool/postfix/pid
(code=exited, status=0/SUCCESS)
Process: 716 ExecStartPre=/usr/libexec/postfix/aliasesdb (code=exited,
status=0/SUCCESS)
Process: 787 ExecStartPre=/usr/libexec/postfix/chroot-update (code=exited,
status=0/SUCCESS)
Process: 819 ExecStart=/usr/sbin/postfix start (code=exited,
status=0/SUCCESS)
Main PID: 1149 (master)
Tasks: 69 (limit: 48939)
Memory: 6.2G
CPU: 2min 5.479s
[/CODE]
As shown above, postfix was consuming 6.2 GB of RAM before it got killed by OOM
Killer.
Regards,
Mr. Turritopsis Dohrnii Teo En Ming
Targeted Individuals in Singapore
GIMP = Government-Induced Medical Problems
3rd March 2025 Monday
On Sunday, March 2nd, 2025 at 11:08 PM, Wietse Venema via Postfix-users
<[email protected]> 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 memory? Use top, ps, or whatever tool you are
> comfortable with. It's no good to give one nimber for the whole
> system.
>
> Wietse
> _______________________________________________
> Postfix-users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
