gordon@dickens.com writes:
"systemctl stautus mailman" generates the following output:
That's what I expected, consistent with your previous report.
According to my logs, the upgrade from Debian 11 to 12 began at exactly 2023-10-31 13:50. "journalctl -S "2023-10-31 13:50" -u mailman -x" generates the following output:
I didn't want any of that. I just wanted the log from the most recent attempt to start Mailman.
Note that the above journalctl command does not generate any output after 2023-10-31 14:19:43 although I have been running the startup script often.
I'm a SYSV init person. Perhaps the journalctl command I suggested was insufficiently inclusive. But that seems very strange to me.
"ps -e -f | grep mailman" generates the following output:
Hm. This has nothing to do with your problem as far as I know, but why is a uwsgi command in your venv/bin? Debian has a package for that, are you not using it? Did you do anything specific to put uwsgi there?
Oh, wait ... there's a possibility that your best bet is to delete the old venv as inconsistent and create a new one. In that case be sure you know how to get uwsgi installed where your startup scripts expect it.
Basically, it does not appear that mailman nor the runners are active and rebooting does not help. "/opt/mailman/venv/bin/mailman start" generates errors as follows: [...]
pkg_resources.DistributionNotFound: The 'mailman==3.3.5' distribution was not found and is required by the application
3.3.5 is quite old now. Is that the version of Mailman you've installed and were expecting? It seems likely to me that somehow the Mailman package has been upgraded to a more recent version but the venv/bin/mailman command has not been upgraded. Is that command owned by the mailman user?
Steve