
On 2022-10-18 14:29, Mark Sapiro wrote:
FROM: Me via listname@listdomain.com TO: listname@listdomain.com CC: me@mydomain.com
This is expected. See the comment in the code beginning at https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/... for why we do this.
Got it. Thank you.
# ps -fAww |grep python root 432 1 0 00:36 ? 00:00:00 /usr/bin/python3 /usr/bin/fail2ban-server -xf start list 745 1 0 00:38 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/mailmanctl -s start list 751 745 2 00:38 ? 00:00:04 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s nobody 913 911 0 00:40 ? 00:00:00 /usr/bin/python /usr/local/bin/mpanel-memory-graph root 921 908 0 00:40 pts/0 00:00:00 grep python
There should be more. Where are ArchRunner, BounceRunner, CommandRunner, IncomingRunner, NewsRunner, VirginRunner and RetryRunner? Did you edit them out?
What does
ps -fwwu list
show?
I hadn't edited then out, but when I ran "ps -fAww |grep python" again just now, they're all present now. Good to know that all those are supposed to be there (in case there's a "next time"). And "ps -fwwu list" shows the same.
# ps -fAww |grep python root 432 1 0 00:36 ? 00:00:20 /usr/bin/python3 /usr/bin/fail2ban-server -xf start nobody 5348 5343 0 03:45 ? 00:00:00 /usr/bin/python /usr/local/bin/mpanel-memory-graph list 5407 1 0 03:47 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/mailmanctl -s start list 5408 5407 0 03:47 ? 00:00:00 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s list 5409 5407 0 03:47 ? 00:00:00 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s list 5410 5407 0 03:47 ? 00:00:00 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s list 5411 5407 0 03:47 ? 00:00:00 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s list 5412 5407 0 03:47 ? 00:00:00 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s list 5413 5407 0 03:47 ? 00:00:00 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s list 5414 5407 0 03:47 ? 00:00:00 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s list 5415 5407 1 03:47 ? 00:00:00 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s root 5422 5416 0 03:47 pts/0 00:00:00 grep python
/////// DID THAT PID FILE REAPPEAR? # find / -type f -iname "mailman.pid" /////// NO RESULT. ... shrug ...
I suspect an issue with the Debian/Ubuntu package. What is the content of /etc/systemd/system/mailman.service?
# cd /etc/systemd/system/ # ls -la ... mailman-qrunner.service -> /lib/systemd/system/mailman.service
# cat /lib/systemd/system/mailman.service [Unit] Description=Mailman Master Queue Runner After=network.target
[Service] Type=forking PIDFile=/var/run/mailman/mailman.pid ExecStart=/usr/lib/mailman/bin/mailmanctl -s start ExecStop=/usr/lib/mailman/bin/mailmanctl stop ExecReload=/usr/lib/mailman/bin/mailmanctl restart Restart=always RestartSec=3s RestartPreventExitStatus=1
[Install] WantedBy=multi-user.target Alias=mailman-qrunner.service
It seems that it was looking for the PID file in "/run/mailman/mailman.pid" (below) and the above says it lives at "/var/run/mailman/mailman.pid"
Oct 18 00:30:13 syd systemd[1]: mailman.service: Can't open PID file /run/mailman/mailman.pid (yet?) after start: No such file or directory