On 12/28/21 1:28 PM, William Oliver wrote:
If I just stop the thing and then start it, it goes fast. Here's that log:
Dec 28 16:27:22 emergenus systemd[1]: Stopping GNU Mailing List Manager... Dec 28 16:27:24 emergenus mailman[23408]: Shutting down Mailman's master runner Dec 28 16:27:27 emergenus systemd[1]: mailman3.service: Succeeded. Dec 28 16:27:27 emergenus systemd[1]: Stopped GNU Mailing List Manager. Dec 28 16:27:27 emergenus systemd[1]: mailman3.service: Consumed 42.834s CPU time. Dec 28 16:27:27 emergenus systemd[1]: Starting GNU Mailing List Manager... Dec 28 16:27:29 emergenus kernel: [ 8076.868797] [UFW BLOCK] IN=eth0 OUT= MAC=00:16:3e:ef:72:96:00:23:9c:9e:9f:c0:08:00 SRC=92.63.197.108 DST=203.159.80.234 LEN=40 TOS=0x00 PREC=0x00 TTL=253 ID=58971 PROTO=TCP SPT=44610 DPT=21987 WINDOW=1024 RES=0x00 SYN URGP=0 Dec 28 16:27:29 emergenus mailman[23433]: Starting Mailman's master runner Dec 28 16:27:29 emergenus mailman[23433]: Generating MTA alias maps
These log entries are from restarting mailman, not mailmanweb.
Dec 28 16:27:30 emergenus systemd[1]: mailman3.service: Can't open PID file /opt/mailman/mm/var/master.pid (yet?) after start: Operation not permitted
I don't know what's up with the pid thing -- it moves right on in about 1 second.
It's a race condition. systemd (systemctl start) is trying to read /opt/mailman/mm/var/master.pid before the master has created it. That's why it says (yet?).
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan