On 3/22/26 10:56 PM, Thomas Krichel wrote:
But mailman-web processes are still runningroot@darni ~ # ps axf | grep mailman-web 532703 pts/4 S+ 0:00 \_ grep mailman-web 516993 ? Ss 0:00 /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings 517012 ? S 0:05 \_ /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings 517014 ? S 0:00 \_ /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings 517015 ? S 0:00 \_ /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings 517016 ? S 0:00 \_ /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings 517017 ? S 2:09 \_ /usr/local/mailman/venv/bin/python3.13 /usr/local/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings
These are qcluster processes. They are normally started and stopped separately from mailmanweb. See <https://docs.mailman3.org/en/latest/install/virtualenv.html#automatically-st...>.
You also need systemctl stop qcluster
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan