Your message dated Wed, 23 Jan 2019 00:20:54 +0000 with message-id <e1gm6hm-0003rx...@fasolo.debian.org> and subject line Bug#919158: fixed in mailman-suite 0+20180916-3 has caused the Debian Bug report #919158, regarding mailman3-web: cronjobs should be run with flock to avoid them running amok to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: mailman3-web Version: 0+20180916-2~bpo9+1 Severity: serious Dear Maintainer, mailman3-web cronjobs (django-admin runjobs minutely as worst) are run without flock. When the system is (temporarily) constrained on resources, this can cause a severe backlog of django-admin runjobs, grinding the system to a halt. This is not fun: root 961 0.0 0.0 76116 104 ? S 10:44 0:00 /usr/sbin/CRON -f www-data 962 0.0 0.0 4288 0 ? Ss 10:44 0:00 /bin/sh -c [ -f /usr/bin/django-admin ] && python3 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings www-data 963 0.3 0.0 343884 1808 ? Sl 10:44 0:12 python3 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings root 1330 0.0 0.0 76116 108 ? S 10:45 0:00 /usr/sbin/CRON -f www-data 1335 0.0 0.0 4288 0 ? Ss 10:45 0:00 /bin/sh -c [ -f /usr/bin/django-admin ] && python3 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings www-data 1337 0.2 0.2 339696 10836 ? Sl 10:45 0:08 python3 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings Ad infinitum # pidof -x python3 13186 12884 12592 12304 11987 11596 11154 11103 10890 10889 10888 10887 10886 10857 10607 10260 10206 10068 9671 9371 9021 8551 7579 7096 6646 6315 5983 5662 5351 5029 4705 4394 3974 3643 2976 2405 2357 2041 2036 1680 1337 963 # uptime 11:48:37 up 29 days, 3:46, 21 users, load average: 110.60, 99.61, 73.86 # kill -9 $(pidof -x python3) -bash: fork: Cannot allocate memory My PTSD now recommends prefixing each job in /etc/cron.d/mailman3-web with a flock -n call: * * * * * www-data [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.minutely python3 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings 2,17,32,47 * * * * www-data [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.quarter_hourly python3 /usr/bin/django-admin runjobs quarter_hourly --pythonpath /usr/share/mailman3-web --settings settings @hourly www-data [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.hourly python3 /usr/bin/django-admin runjobs hourly --pythonpath /usr/share/mailman3-web --settings settings @daily www-data [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.daily python3 /usr/bin/django-admin runjobs daily --pythonpath /usr/share/mailman3-web --settings settings @weekly www-data [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.weekly python3 /usr/bin/django-admin runjobs weekly --pythonpath /usr/share/mailman3-web --settings settings @monthly www-data [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.monthly python3 /usr/bin/django-admin runjobs monthly --pythonpath /usr/share/mailman3-web --settings settings @yearly www-data [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.yearly python3 /usr/bin/django-admin runjobs yearly --pythonpath /usr/share/mailman3-web --settings settings Let me know if you want a patch. By the way, is there a reason why /usr/share/mailman3-web/manage.py is not used throughout the mailman3-web package instead of "/usr/bin/django-admin --pythonpath /usr/share/mailman3-web --settings settings"? Because that's basically what the manage.py wrapper does. -- Sampo Sorsa
--- End Message ---
--- Begin Message ---Source: mailman-suite Source-Version: 0+20180916-3 We believe that the bug you reported is fixed in the latest version of mailman-suite, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre-Elliott Bécue <p...@debian.org> (supplier of updated mailman-suite package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Wed, 23 Jan 2019 00:39:29 +0100 Source: mailman-suite Binary: mailman3-web Architecture: source Version: 0+20180916-3 Distribution: unstable Urgency: medium Maintainer: Debian Mailman Team <pkg-mailman-hack...@lists.alioth.debian.org> Changed-By: Pierre-Elliott Bécue <p...@debian.org> Description: mailman3-web - Django project integrating Mailman3 Postorius and HyperKitty Closes: 917548 919154 919158 Changes: mailman-suite (0+20180916-3) unstable; urgency=medium . [ Jonas Meurer ] * d/mailman3-web.mailman3-web-qcluster.service: - Fix path to python3 interpreter (Closes: #919154) . [ Pierre-Elliott Bécue ] * d/mailman3-web.postinst: - Avoid dpkg -s call for the upgrade_fixes, and call the fix only on appropriate upgrade. Will re-do it for all upgrades to -3. * d/mailman3-web.postrm: - Typo: ngnx_remove => nginx_remove. (Closes: #917548) * d/mailman3-web.cron.d: - Use /u/s/mailman3-web/manage.py instead of a call to django-admin and use flock to avoid piling up cron processes. (Closes: #919158) * d/control - Bump Standards-Version to 4.3.0 Checksums-Sha1: cba72d97e3e654d721ffbed3b4f7c4a8b8fd8ae8 2053 mailman-suite_0+20180916-3.dsc 9fbd4c988fe80d84f8a1288a3fdef5a330307718 25520 mailman-suite_0+20180916-3.debian.tar.xz 4887cc5379bc011444a1e6b4ea7c477a1ec91149 5513 mailman-suite_0+20180916-3_amd64.buildinfo Checksums-Sha256: 9b11b5be1ed03b5cf16d50581bbb01f7204ccb9e401483c5a36b20ea5d381056 2053 mailman-suite_0+20180916-3.dsc 3f1ecd1338378d019b38f13422bfeda52fcf040a158706df5c9218cd4b1e93a0 25520 mailman-suite_0+20180916-3.debian.tar.xz ea80e51c5055b8194cc7e347491c600b4c7fe13efce7de6d07b7f5a91bfbb8c5 5513 mailman-suite_0+20180916-3_amd64.buildinfo Files: 33cfea0b6571fa36f317588421cb7bdf 2053 web optional mailman-suite_0+20180916-3.dsc 0dc796d112b332ca41dceb00d4b4c022 25520 web optional mailman-suite_0+20180916-3.debian.tar.xz 3b71240881b2f998b2385fd6b22936b2 5513 web optional mailman-suite_0+20180916-3_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEESYqTBWsFJgT6y8ijKb+g0HkpCsoFAlxHrRUACgkQKb+g0Hkp Csp4Xw/8CcUcRYLec/Kd9bXyWI/WA2ssUgP9DvKvYRT6Vq7zmn2fNc8343DqIR72 KsD3zIRZ/G8wSojc7WtHTqwiZgbIB78pG/oWou0bAgTAVsTJZ2bY123BZwW55hmI 3NmhyhPWvjs8Ba9lvkJiYJX6g4dw9XT+y8abUp+yoc9+cJQ+yx67L+CosegvZ9No OvCNUBi/tATztMQABTy1ufE5Pzrc4y3M/butUbQ6es/UcH6e/+lgmrwvuxwUDt8e zxrUFnKC/GthKql2y2yAs6kiKMhIYMw4baVatb5ZcEfDQ7hjIC2wi5I6sQ0unPaD VUsAGqJ8Qa7Gm0gXBGFOzQFmBoXu+hz0W3cZ0qAyzKVyFnEEpB2E5AHVIN5kpYB8 afvSzhJoty4/Nh3T6nxya3rFnw75vb5ZZbxsK++JSRegqm2/UMzgPKAd9erUy7OP kTqmmzD4DhUStkir5bapTgDGnH927wsERq33+wqKE/D+MP6Yy2r0CJMTjBefXIWs ZdMknKtGwNWER6pKDxrZ5gSJ/X3hj82ff+ZjsIx80h2BgM0GGLTVb3X35vJnMaJr yI8Sd1d+00UaX+vTFD2Xr3HT03rTcWnlApsTbeh5WkxT/TKNLXgR5KPnk3vR7Ske nY7EjHwgSSOmPwWli5Y17IcRHQKccBcnU9VVINJblvtMvCGMtic= =GcGZ -----END PGP SIGNATURE-----
--- End Message ---
