[MM3-users] Re: Message shows up individually but not in the thread

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:

# Mailman jobs
@daily             mailman  bash -c 'cd /home/mailman && . /home/mailman/env3/bin/activate && mailman digests --send'
@hourly            mailman  bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs hourly         --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings'
@daily             mailman  bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs daily          --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings'
@weekly            mailman  bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs weekly         --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings'
@monthly           mailman  bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs monthly        --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings'
@yearly            mailman  bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs yearly         --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings'
* * * * *          mailman  bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs minutely       --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings'
2,17,32,47 * * * * mailman  bash -c 'cd /home/mailman && . /home/mailman/env2/bin/activate && django-admin runjobs quarter_hourly --pythonpath /home/mailman/mailman-suite/mailman-suite_project --settings settings

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 qcluster

And the qcluster process shows both up in the process list and is happily logging away in the uWSGI log.

Greetings Marvin

• 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.

-- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F