On Thu, Jan 22, 2026 at 10:07 PM Stephen J. Turnbull <[email protected]> wrote:
> Washington Odhiambo via Mailman-users writes: > > > For some reason, my mailmanweb (I am using Gunicorn) has been > > misbehaving lately. The last change I ever made to my MM3 > > installation is when I applied the patch mentioned in this thread. > > The patch seems very simple, I don't see why it would cause the > problems you see. Are there any other changes vs. the stock version > you have? > None. > The misbehavior manifests in the Postrorius web UI becoming > > inaccessible, much as mailmanweb is running. Checking on its > > status, I see very high RAM utilization: > > I don't see anything consistent in these tracebacks except that > eventually a worker gets killed because of out of memory or timeout. > It seems that you are just in a situation of extreme memory pressure. > I have not been in close contact with this situation ever since I switched to Gunicorn. And TBH, I have not seen any OOMs happening on the host. Many multiprocess or multithread server implementations have a tuning > parameter where each task is limited to processing N requests, then it > exits and a new one is initialized. If gunicorn has such a feature, > lowering the number of tasks before exit might help keep memory usage > down if there's a leak. > > Or you could try experimenting with higher memory allocations to these > processes if that is possible (I'm not suggesting that as a production > solution, it's an experiment to see what happens). > I am only having issues with mailmanweb. No other application - unless I haven't realized it. > > You could also try turning off markdown processing to see if that > alleviates the memory pressure (I can't see why that would help, but > it's a known difference in your instance from stock which doesn't seem > to have such heavy memory usage elsewhere). Again, this is an > experiment to try to localize the problem, not a suggestion for a > solution. > I don't have markdown enabled. IIRC, we checked this last time. I hope Mark or another user has some idea, but I don't, sorry. > Hopefully. Thanks. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] _______________________________________________ Mailman-users mailing list -- [email protected] To unsubscribe send an email to [email protected] https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/[email protected]/message/4QYSXGIGUZIIWHKKATNXAGDHFCMCSALK/ This message sent to [email protected]
