za...@mta.ca writes: > web interface but I see the error "Mailman REST API not > available. Please start Mailman core." I can su to the mailman user > and run 'mailman start -f' which seems to get things going again > and shows the lists as they were before the snapshot, which is > good, but I would like to get the issue fixed so that services > start normally.
Have you done "systemctl restart mailman3" since running "mailman start -f"? The only thing that the "-f" (or "--force") flag does is to try to delete the stale master lock safely. Since Mailman did start, it did delete that lock. I expect that now it should start successfully without further exceptional intervention. We now recommed putting --force in the ExecStart line of the mailman3.service unit. I suppose it is possible to corrupt the database by snapshotting without stopping, but PostgreSQL and MySQL are quite robust to that kind of thing. You should continue to watch for weird behavior, but I would think you should run normally now. > Any help is appreciated. Here is some terminal output: I don't see anything there that suggests you're not ready to go. -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-le...@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/5RMPLV4W6BGU5KA5H5R3EGCC63YG2HZL/ This message sent to arch...@mail-archive.com
