Suddenly, at digest #551, one of our lists stopped digesting properly.
1) Articles accumulate in proper directory
2) Digest get sent out with all articles in directory
3) * Directory does NOT get cleared out
4) After another message comes in, the digest gets triggered with n+1 articles
All other digests are working OK. Has anyone else ever seen this happen?
1) v. 1.93 (yeah, we're planning to upgrade)
2) digest-config set at
# maxlength [integer] (40000) <resend,digest>
# The maximum size of an unapproved message in characters. When used
# with digest, a new digest will be automatically generated if the
# size of the digest exceeds this number of characters.
maxlength = 58000
This is a list with huge volume and normally has multiple digests per day
3) relevant aliases look like
listname-digest-request: "|/majordomo/majordomo/wrapper majordomo -l pafun-digest"
listname-foo: :include:/majordomo/lists/pafun, pafun-archive, "|/majordomo/majordomo/wrapper digest -r -C -l pafun-digest pafun-digest-foo"
4) digest looked like
-rw-rw---- 1 majordom majordom 38728 Mar 3 12:42 v01.n550
-rw-rw---- 1 majordom majordom 269815 Mar 4 12:39 v01.n551
-rw-rw---- 1 majordom majordom 370017 Mar 5 15:06 v01.n556
5) Steps taken to try to resolve...
Figuring that this was a temporary problem caused by high load (the mail
deliverer stalled for a while yesterday), I
a) removed all files in the /majordomo/digest dir
b) split digest manually into parts for the sake of the archives
c) incremented digest_issue in the config file to 556
but the same thing kept happening today: multiple, multiple copies of the
digest, increasing by one article each time.
Now, I've removed the subscriber list and we'll ship them the ones we
missed... but does anyone know how to stop this? I've seen people (sorry,
forgot who) report that you can go up to #999 and beyond. This is the list
with the highest digest issue number for us, but I find it hard to believe that
we're hitting some kind of MD limit here.
-rw-rw-r-- 1 majordom majordom 9001 Mar 5 15:02 listname
-rw-rw-r-- 1 majordom majordom 62 Mar 5 15:02 listname-digest
-rw-r--r-- 1 majordom majordom 12970 Mar 4 12:46 listname-digest.config
-rw-r--r-- 1 majordom majordom 10259 Mar 3 15:07 listname-digest.config.out
-rw-r--r-- 1 majordom majordom 1197 Mar 3 14:45 listname-digest.info
-rw-r--r-- 1 majordom majordom 12839 Mar 3 14:45 listname.config
-rw-r--r-- 1 majordom majordom 1141 Mar 5 15:00 listname.info
We _may_ have done something that messed up the permissions on the subscriber
files... can't see how that would affect digesting, though, and I fixed it
7) System: an intel linux/perl 4.036 setup that's been working nearly
perfectly for over a year.
Any help appreciated... I'm about to increment the digest volume number to see
if that helps.