Page MenuHomePhabricator

mailman cronjobs not running?
Closed, ResolvedPublic

Description

it was an action item in the last meeting to double check mailman's own cron jobs are running

apparently they are not, since we have 2.5G of files in ./data/shunt/ and the default would be that these get deleted after 7 days.

instead:

12:28 < JohnFLewis> mutante: clearly cron isn't being ran
12:29 < JohnFLewis> default is set to kill after 7 days; oldest file in shunt is about lily->sodium
12:29 < JohnFLewis> so 2012 :)

Event Timeline

Dzahn created this task.Aug 26 2015, 7:33 PM
Dzahn claimed this task.
Dzahn reassigned this task from Dzahn to JohnLewis.
Dzahn raised the priority of this task from to High.
Dzahn updated the task description. (Show Details)
Dzahn added subscribers: ori, MZMcBride, Dzahn and 5 others.

[sodium:~] $ sudo crontab -u list -l
no crontab for list

Dzahn added a comment.Aug 26 2015, 7:35 PM

meanwhile running find to delete all those files older than 7 days on the target on fermium

Dzahn added a comment.Aug 26 2015, 7:38 PM
[sodium:/etc/cron.d] $ cat mailman 
# At 8AM every day, mail reminders to admins as to pending requests.
# They are less likely to ignore these reminders if they're mailed
# early in the morning, but of course, this is local time... ;)
0 8 * * * list [ -x /usr/lib/mailman/cron/checkdbs ] && /usr/lib/mailman/cron/checkdbs
#
# At 9AM, send notifications to disabled members that are due to be
# reminded to re-enable their accounts.
0 9 * * * list [ -x /usr/lib/mailman/cron/disabled ] && /usr/lib/mailman/cron/disabled
#
# Noon, mail digests for lists that do periodic as well as threshold delivery.
0 12 * * * list [ -x /usr/lib/mailman/cron/senddigests ] && /usr/lib/mailman/cron/senddigests
#
# 5 AM on the first of each month, mail out password reminders.
0 5 1 * * list [ -x /usr/lib/mailman/cron/mailpasswds ] && /usr/lib/mailman/cron/mailpasswds
#
# Every 5 mins, try to gate news to mail.  You can comment this one out
# if you don't want to allow gating, or don't have any going on right now,
# or want to exclusively use a callback strategy instead of polling.
# */5 * * * * list [ -x /usr/lib/mailman/cron/gate_news ] && /usr/lib/mailman/cron/gate_news
#
# At 3:27am every night, regenerate the gzip'd archive file.  Only
# turn this on if the internal archiver is used and
# GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py
27 3 * * * list [ -x /usr/lib/mailman/cron/nightly_gzip ] && /usr/lib/mailman/cron/nightly_gzip

So crons do run - just not all jobs.

johnflewis@fermium:/var/lib/mailman/cron$ cat crontab.in
# At 8AM every day, mail reminders to admins as to pending requests.
# They are less likely to ignore these reminders if they're mailed
# early in the morning, but of course, this is local time... ;)
0 8 * * * /usr/bin/python -S /var/lib/mailman/cron/checkdbs
#
# At 9AM, send notifications to disabled members that are due to be
# reminded to re-enable their accounts.
0 9 * * * /usr/bin/python -S /var/lib/mailman/cron/disabled
#
# Noon, mail digests for lists that do periodic as well as threshhold delivery.
0 12 * * * /usr/bin/python -S /var/lib/mailman/cron/senddigests
#
# 5 AM on the first of each month, mail out password reminders.
0 5 1 * * /usr/bin/python -S /var/lib/mailman/cron/mailpasswds
#
# Every 5 mins, try to gate news to mail.  You can comment this one out
# if you don't want to allow gating, or don't have any going on right now,
# or want to exclusively use a callback strategy instead of polling.
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/bin/python -S /var/lib/mailman/cron/gate_news
#
# At 3:27am every night, regenerate the gzip'd archive file.  Only
# turn this on if the internal archiver is used and
# GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py
27 3 * * * /usr/bin/python -S /var/lib/mailman/cron/nightly_gzip
#
# At 4:30AM daily, cull old entries from the 'bad' and 'shunt' queues.
30 4 * * * /usr/bin/python -S /var/lib/mailman/cron/cull_bad_shunt

That is the full crontab file for a 2.1.18 install, which can do the above approach or we can have these in list's crontab. It seems only the cronjob we're interested in, is missing. I'm interesting what lily's version was and if the old cron was just copied and the new one not applied. That, or, mailman added the cron late.

JohnLewis closed this task as Resolved.Aug 26 2015, 7:46 PM

http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1086 adds the cron we're interested.

My bet is we're using the crons lily had and not what sodium should. They work, just out of date from pre-2008. Nothing has died and no one has noticed since 2012 so clearly not a massive issue.