On 12/2/22 08:21, Odhiambo Washington wrote:
I am facing an odd situation in which MM3 doesn't start successfully on reboot, but I can start it manually. This is a venv install. This started after I did an upgrade (pip install --upgrade mailman postorius hyperkitty mailman-hyperkitty) followed by the requisite collectstatic|compress|compilemessages|migrate post-update commands.
Was the venv activated when you ran pip?
You should also include django-mailman3 and mailmanclient in the packages to be upgraded although they are dependencies and "should" upgrade anyway.
Also, at least one person has noted that --force-reinstall was required to get all dependencies upgraded <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/OLISJTCOMZKBHDCRR3XET7E5RZIQCMYI/>
Secondly, it appears that the upgrade did NOT change the versions for the upgraded components - postorius=1.3.6, hyperkitty=1.3.5, Mailman Core Version=3.3.5. I was expecting the version to all bump up to the latest.
What does pip freeze in the venv show for versions?
Thanks in advance for any insights into what could be causing this.
How do you start it manually? mailman start or systemctl start mailman3? What's the content of /etc/systemd/system/mailman3.service?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan