Package: python3-django-hyperkitty
Version: 1.3.5.0-2
Severity: wishlist
Dear Maintainer,
Thank you for your work on mailman3.
As I noted in another report, when there are issues with the django
configuration, this leads to a huge volume of cron errors into a sysadmin
inbox. Rather than commenting out all the lines in /etc/cron.d/mailman3-web I
have added a test as to whether the service is active.
The test I am using is
systemctl is-active --quiet mailman3-web
Therefore, when I issue:
systemctl stop mailman3-web
(because it is currently broken anyway), it also has the effect of stopping the
cron tasks in the framework. Might you consider making this change in the
packaged cron.d file?
Kind regards,
CT.
My new /etc/cron.d/mailman3-web file below
* * * * * www-data [ -f /usr/bin/django-admin ] && systemctl
is-active --quiet mailman3-web && flock -n /var/run/mailman3-web/cron.minutely
/usr/share/mailman3-web/manage.py runjobs minutely
2,17,32,47 * * * * www-data [ -f /usr/bin/django-admin ] && systemctl
is-active --quiet mailman3-web && flock -n
/var/run/mailman3-web/cron.quarter_hourly /usr/share/mailman3-web/manage.py
runjobs quarter_hourly
@hourly www-data [ -f /usr/bin/django-admin ] && systemctl
is-active --quiet mailman3-web && flock -n /var/run/mailman3-web/cron.hourly
/usr/share/mailman3-web/manage.py runjobs hourly
@daily www-data [ -f /usr/bin/django-admin ] && systemctl
is-active --quiet mailman3-web && flock -n /var/run/mailman3-web/cron.daily
/usr/share/mailman3-web/manage.py runjobs daily
@weekly www-data [ -f /usr/bin/django-admin ] && systemctl
is-active --quiet mailman3-web && flock -n /var/run/mailman3-web/cron.weekly
/usr/share/mailman3-web/manage.py runjobs weekly
@monthly www-data [ -f /usr/bin/django-admin ] && systemctl
is-active --quiet mailman3-web && flock -n /var/run/mailman3-web/cron.monthly
/usr/share/mailman3-web/manage.py runjobs monthly
@yearly www-data [ -f /usr/bin/django-admin ] && systemctl
is-active --quiet mailman3-web && flock -n /var/run/mailman3-web/cron.yearly
/usr/share/mailman3-web/manage.py runjobs yearly
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.16.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-django-hyperkitty depends on:
ii fonts-glyphicons-halflings 1.009~3.4.1+dfsg-2
ii libjs-bootstrap4 4.6.1+dfsg1-1
ii libjs-sphinxdoc 4.3.2-1
ii python3 3.9.8-1
ii python3-dateutil 2.8.1-6
ii python3-django 2:3.2.12-2
ii python3-django-compressor 2.4.1-2
ii python3-django-extensions 3.1.5-2
ii python3-django-gravatar2 1.4.4-2
ii python3-django-haystack 3.1.1-1
ii python3-django-mailman3 1.3.7-1
ii python3-django-q 1.3.9-3
ii python3-djangorestframework 3.12.4-2.1
ii python3-elasticsearch 7.16.2-1
ii python3-flufl.lock 5.0.1-1
ii python3-mailmanclient 3.3.3-1
ii python3-mistune 2.0.0-1+really0.8.4-1
ii python3-networkx 2.5+ds-2
ii python3-robot-detection 0.4.0-2
ii python3-tz 2022.1-1
Versions of packages python3-django-hyperkitty recommends:
ii mailman3-web 0+20200530-2
python3-django-hyperkitty suggests no packages.
-- no debconf information
