I updated the number of runners in hyperkitty to 9 a couple days ago to address a problem I was having with custom templates per this thread <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/MA4QOTYHKFBZQDCVH4E4V2ANFAJHJCRB/#UHNTDXGANCB3EQ2TR2YOB34W22FAYEKV>. I reduced this to 2 workers and so far it seems to have resolved the problem. Thanks again for everyone's help. The Mailman community gets an A+ for its treatment of noobs!
Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Fri, Jan 31, 2025 at 2:44 AM Stephen J. Turnbull < turnb...@sk.tsukuba.ac.jp> wrote: > Arte Chambers via Mailman-users writes: > > > The output from systemctl status after mailman has failed > > ``` > > ~$ sudo systemctl status mailman3.service > > × mailman3.service - GNU Mailing List Manager > > Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; > preset: > > enabled) > > Active: failed (Result: oom-kill) since Thu 2025-01-30 17:00:27 > UTC; > > Ah, yes, that is as dead as the Monty Python parrot. How much memory > and swap does the system have? (Note, you probably don't want to be > using swap at all most of the time, this is to understand the "killed > because the system ran out of free memory" oom-kill message.) > > For comparison, I found that OOM kills were fairly frequent (~ once in > 1-3 days) on a Digital Ocean droplet with 2GB of memory, and there was > a dramatic reduction but not an elimination of OOM kills when I bumped > it to 4GB. The two active apps were Mailman and Mediawiki, plus > whatever Digital Ocean likes to run on its standard droplets. > > Steve > _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-le...@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/PD5UXPVMQ53MWSZB77QBB7XQVRYN7XDY/ This message sent to arch...@mail-archive.com
