On 12/27/22 01:23, Odhiambo Washington wrote:
I have actually deactivated mine, and life is still good with my MM3.
And just so that my mind is in the clear, there are three ways of getting the full MM3 functionality, viz:
- Mailman core, Django's cluster, and Gunicorn
- Mailman core, Django's cluster, and uWSGI
- Mailman core, Django's cluster, and mod_wsgi
Yes, and possibly there are other WSGI interfaces, but offhand I don't know.
And something that has not been quite clear to me: What is the purpose of Django's cluster in all this?
django_q <https://django-q.readthedocs.io/en/latest/> is an app for Django that can process tasks asynchronously in the background so they don't block the foreground. qcluster manages those tasks.
I am asking because on my FreeBSD server, I usually see not less than 30 PIDs for:
/opt/mailman/mm/venv/bin/python3 /opt/mailman/mm/venv/bin/django-admin qcluster --pythonpath /opt/mailman/mm/ --settings settings (python3.9)
And there is a time I found it having 240 PIDs. Would there be a problem if I limit the number of workers to "8"? Some of those may be orphaned. On servers I manage, I regularly stop all mailman3 services to install updates and on one of these servers (only mail.python.org) where there are resource issues, when the services are stopped, there are still orphaned qcluster processes. I have this
#! /bin/bash
if status qcluster | grep -q 'running' ; then
echo qcluster is running
exit
fi
ps -fwwu mailman|grep '[a]dmin qcluster'|awk '{print $2}'|xargs kill
to get rid of the orphans
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan