Just mostly out of curiousity: why don't you install as venv or docker? Then it would be somewhat more independent of underlying OS and somewhat more up to date...
I also did the installation first with the Debian-packages when moving in from mailman2, but fortunately realised quite fast, that there might be a bunch of problems. Also the last years I read on this list gave me the impression, that there are quite often problems with the Debian-packaged-installation that arise while installing ... or later when upgrading the OS. I'm quite happy with docker right now (and hope that it's kept up to date for some time longer :-D ... thanks in any cases!).
Regards, Jens.
Am 26.08.23 um 14:54 schrieb Franklin Weng:
The problem was reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041681
AND here:
https://gitlab.com/mailman/django-mailman3/-/issues/68
Not sure which it should belong to. There are screenshots in the bug report, but some users said they couldn't open our Nextcloud instance. If you have problems opening the screenshots too you can give me a private mail I'll send pictures to you.
And - honestly I ran a mm3 instance on Debian Buster (10) a few years ago, and when I tried to upgrade my Buster to Bullseye the mm3 was totally broken. Fortunately I made a VM snapshot before upgrading so I reverted it back. However that instance was unstable too - it would run out of memory about every two weeks, so I had to setup a cron to reboot the VM every week. I have no idea what happened. It was pretty frustrated.
Then we moved all our services to another server hosts and I decided to rebuild the mm3 instances. I tried to build-remove-rebuild several times, including building it on Bullseye but got a lot of database locked errors, then tried it on Bookworm and got a broken django admin page, and finally set up a pretty stable instance on Bullseye which has run for about 6 weeks without any problem. So I decided to share the progress and what I found.
Hope it helps.
Franklin