On Mon, Apr 28, 2025 at 4:45 PM <zachr@mta.ca> wrote:

I made a snapshot of my mailman3 VM before running a script to modify a bunch of lists. I stupidly did not turn the VM off before I made the snapshot, so Im almost certain this is a corrupted DB problem from doing a snapshot restore. The issue is now that the mailman service will not start automatically. Im able to get to the 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. Any help is appreciated. Here is some terminal output:

''' root@mlist3:~# systemctl status mailman3 × mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Mon 2025-04-28 13:24:43 UTC; 1min 39s ago Process: 1873 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=2) CPU: 776ms

Apr 28 13:24:42 mlist3 systemd[1]: Starting mailman3.service - GNU Mailing List Manager... Apr 28 13:24:43 mlist3 mailman[1873]: Usage: mailman start [OPTIONS] Apr 28 13:24:43 mlist3 mailman[1873]: Try 'mailman start -h' for help. Apr 28 13:24:43 mlist3 mailman[1873]: Error: A previous run of GNU Mailman did not exit cleanly (stale_lock). Try using --force

cd /opt/mailman/var/locks/ rm *master*

Then start mailman,

-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]