On 3/27/21 5:13 AM, Christine wrote:
Hi, I have been using mailman for about ten years, now I want to move the lists to another server, I have installed mailman3 there, most of it seems to be running, but the "rest api runner" is not. Nothing is listening on port 8001. What have I missed? What do I do to start the restapi runner? I checked the logs, I don't see anything suspicious.
this is what systemctl status says:
root@lists:~# systemctl status mailman3 ● mailman3.service - Mailman3 server Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: failed (Result: timeout) since Sat 2021-03-27 12:04:06 UTC; 6min ago Docs: man:mailman(1) https://mailman.readthedocs.io/ Process: 173111 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force (code=killed, signal=TERM)
Mar 27 12:02:36 lists systemd[1]: Starting Mailman3 server... Mar 27 12:04:06 lists systemd[1]: mailman3.service: start operation timed out. Terminating. Mar 27 12:04:06 lists systemd[1]: mailman3.service: Failed with result 'timeout'. Mar 27 12:04:06 lists systemd[1]: Failed to start Mailman3 server.
Nothing is listening on port 8001 because apparently Mailman core failed to start.
There is nothing in mailman.log, nor in smtp.log
What Mailman package is installed? Perhaps you should contact the packager for support.
Can you run the mailman command manually, e.g.
sudo -u xxx mailman -C /etc/mailman3/mailman.cfg
where xxx is the Mailman user which if I'm guessing correctly that
this is a debian/ubuntu package, is list. Otherwise it might be mailman.
That should just produce a list of mailman subcommands. If that works, try
sudo -u xxx mailman -C /etc/mailman3/mailman.cfg info
and
sudo -u xxx mailman -C /etc/mailman3/mailman.cfg start
and see what they produce.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan