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?
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.
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).
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 hope Mark or another user has some idea, but I don't, sorry.
Steve
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan