On Mon, Jul 22, 2024 at 9:06 PM Christian via Mailman-users < mailman-users@mailman3.org> wrote:
I recently upgraded Debian 10 'buster' and when I logged in to Postorius in the browser I got the ' Mailman REST API not available. Please start Mailman core' message. So I started it up from the command line doing 'sudo -u mailman /opt/mailman/mm/venv/bin/mailman start -f' which yielded
You upgraded Debian from Buster to what??? Bullseye or Bookworm? Why not just 'sudo systemctl start mailman'?
Starting Mailman's master runner Generating MTA alias maps mailman@lists:
Now when I do ' https://lists.ccalternatives.org/mailman3/lists/?all-lists ' in my browser I get the message ' There are currently no mailing lists.' Meanwhile their archives exist. Are the lists actually gone or ?
The lists are there since your DB is intact and your venv is intact as well.
What am I doing wrong/what's going on here please? Thank you in advance.
I suspect your Python was upgraded to a version different than the one you use to create your virtualenv in the 1st place. If that is the case, you'll need to create a new virtualenv and migrate the data.
One more thing...I am running mailman core version GNU Mailman 3.3.5, Core API Version 3.1, and Core Python Version 3.7.3.
Is there a reason you did not upgrade MM3 core and MM3 Web all this time?
Anyway, check the version of Python used to build your virtualenv against the system version after you upgraded:
# cat /opt/mailman/mm/venv/pyvenv.cfg home = /usr/local/bin include-system-site-packages = false version = 3.11.2 executable = /usr/local/bin/python3.11 command = /usr/local/bin/python -m venv /opt/mailman/mm/venv
If older than the system version, you just need to build a new virtualenv and migrate the data.
HTH.
-- 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]