On 11/04/2017 01:19 AM, Marvin Gülker wrote:
Am 03. November 2017 um 12:35 Uhr -0700 schrieb Mark Sapiro <mark@msapiro.net>:
Are you running all of Django's periodic tasks?
They are running. This is the excerpt from /etc/crontab: ... Obviously, mailman-suite is installed at /home/mailman/mailman-suite and owned by user 'mailman', with the actual Django project in the subdirectory 'mailman-suite_project', just as cloned from the Git repository. The only difference from the official guide here is that I took the liberty to place Mailman into two virtualenvs (a Python2 one for the Django project, and a Python3 one for Mailman-Core*).
There are no errors reported with this in /var/log/cron.log. And before you ask, the task queue is running as well. The uWSGI config has this:
# Setup the django_q related worker processes. attach-daemon = ./manage.py qclusterAnd the qcluster process shows both up in the process list and is happily logging away in the uWSGI log.
There is a possibly related issues at <https://gitlab.com/mailman/hyperkitty/issues/151> and some older ones at <https://gitlab.com/mailman/hyperkitty/issues/131> and <https://gitlab.com/mailman/hyperkitty/issues/149>.
I'm sorry I can't offer more help than that at this point.
- It'd be great if the mailman-suite was moved to Python 3 at some point. That way one wouldn't need two separate virtualenvs.
We're working on moving Postorius and HyperKitty to MM 3.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan