Dennis Putnam via Mailman-users writes:
> Thanks for the info. I thought I had followed everything but I an
> unable to start mailman3 because all the expected directories in
> /var are missing. What steps did I miss?
If you are setting up according to the virtual environment
instructions, Mailman shouldn't be looking for anything in /var that
you didn't explicitly configure to be there.
With the venv active, try running just "mailman info". If that
succeeds and reports something other than /etc/mailman3/mailman.cfg,
then check the file it reports for "layout" and "var_dir" settings,
and remove the var_dir hierachy because it's just confusing. Then run
mailman -C /etc/mailman3/mailman.cfg info
If that succeeds, try starting Mailman with
mailman -f -C /etc/mailman3/mailman.cfg start
The "-f" is short for "--force" and it just cleans up any stale lock
files that might prevent Mailman from starting. (We now recommend
using it in the init script or systemd unit file ExecStart command.)
If either of those fails, or Mailman starts but "doesn't work", look
in the logs (systemctl status, journalctl -eu, and
$var_dir/logs/mailman.log for error messages, and send those along
with /etc/mailman3/mailman.cfg to us. In the case of "doesn't work",
tell us what you mean by "doesn't work": Mailman doesn't accept mail,
Mailman crashes, Mailman doesn't send mail, etc.
--
GNU Mailman consultant (installation, migration, customization)
Sirius Open Source https://www.siriusopensource.com/
Software systems consulting in Europe, North America, and Japan
_______________________________________________
Mailman-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/archives/list/[email protected]/message/M2METQJNDCPTACFRVYCGOXVVXSL7O3XG/
This message sent to [email protected]
