On 7/27/20 9:52 PM, joseverde@gmail.com wrote:
The settings match the Django settings, yes. As far as the rest runner, the following shows on that command:
root 25868 25475 0 21:50 pts/0 00:00:00 grep --color=auto runner=rest
So the rest runner is not running as all you see is your grep command.
On 7/27/20 10:34 PM, joseverde@gmail.com wrote:
On 7/27/20 10:34 PM, joseverde@gmail.com wrote:
And one last infopoint for tonight, I checked on a whim to see if mailman3 was still running, it wasn't since the last time I checked. (the command mailman status, on the other hand, shows it is up and running. The following error was shown when starting to start:
Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: File "/usr/lib/python3/dist-packages/mailman/commands/cli_control.py", line 88, in process Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: status, lock = master_state() Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: File "/usr/lib/python3/dist-packages/mailman/bin/master.py", line 133, in master_state Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: hostname, pid, tempfile = lock.details Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 145, in details Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: with open(self._lockfile) as fp: Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 mailman3[27388]: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/master.lck' Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 systemd[1]: mailman3.service: Control process exited, code=exited status=1 Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 systemd[1]: mailman3.service: Failed with result 'exit-code'. Jul 27 22:30:40 lamp-s-1vcpu-1gb-sfo2-01 systemd[1]: Failed to start Mailman3 server.
It appears there is a permissions issue in trying to read the locks.
Does your systemd script set the user to the Mailman user, and does the Mailman user have read/write permission on Mailman's var/locks/?
Also, is any of Mailman core running? Try
ps -fwwA|egrep 'master|runner'
If a master is running, try
service mailman stop
If that doesn't stop it, send it a sigterm or, only if necessary, a sigkill.
Then if there are an runners left, sigterm them.
Finally if there's anything in var/locks, remove it.
Then try to start Mailman.
Note that if you've previously started Mailman as root, there may be
locks and or other files owned by root that are now inaccessible to
mailman. You may need to chown -R mailman in Mailman's var directory.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan