OK, the problem was solved after a good night's sleep and a fresh look at the
directories. There WAS a .LOCK file in the digest-message-accumulating
directory, but the real problem was a
/majordomo/lists/listname-digest.config.out file that got created and not
deleted back on 3/3 while we had a real high load on the machine. I must
have done an "ls -l /majordomo/lists/listname*" forty times and still didn't
see it until this morning!
recap:
- the articles accumulated, the digest got sent
- the digest issue # did NOT increment, the files didn't get cleared out
- manually forcing the post-digest work (clear out messages and .LOCK,
incrementing the issue number, apologizing to folks who got 250,000-byte
digests) didn't prevent the problem for the next issue
- the digest kept getting sent, with one more article in it each time.
- version 1.93 (Yeah, we're planning to upgrade. You can't just move
150 lists overnight! :) Don't know if this happens in 1.94, but since it's
a good defensive behavior, probably. So, the thing to remember is to look
for BOTH a .LOCK and a *-digest.config.out file if you have a problem
like this out of the blue.
Thanks for the help...
Bonnie Scott
Prodigy, Inc.
> messages and emits another digest. Check the perms on the directory
> containing the individual pre-digested message files (on my system it's
> /usr/majordomo/digests/LISTNAME-digest) and also maybe check if there is
> a leftover .LOCK file (I forget if this is relevant).
>
> -m
Follow-Ups:
References:
|
|
