On 15 Dec 98, at 16:40, Jo Hermans wrote:

> During the last week, we
> have been missing 2 of our digests ; none of our subscribers has received
> them. I haven't received any error-message wither. I mailed the node
> administrator, but he didn't reply yet.
>
> What could be the cause of this problem. I was thinking about a lack of
> diskspace to store the digest (although the regular archive seems to be
> storing just fine). What do you think could be the problem ?
>

One possible cause is that the archives were edited before the digest
containing parts that were edited went out. The digest then gets out of
synch with the archives and can't figure out how to send itself. This is
why we recommend against editing active archive files.

One way you might fix it it to set Digest=No in your header, then turn it
back on after it's had a chance to delete the currently accumulating
digest. You'll lose the current digest (which by now will have grown quite
large), but you'll start over from scratch and future digests will go out on
schedule.

If you can't bear to lose the past digests, the node admin will have to
edit the digest and subject files to make them match the archives, but
this is risky and not generally recommended. Try it at your own risk...

If the archives have not been edited, then you need to look for other
reasons. The node admin should be able to look in the LISTSERV log to
see where the digests are being produced (or attempting to be
produced) and see what is happening. If the logs show the digests going
out without a problem, then it may be a mail server problem (perhaps a
limit on the size of messages it will handle).

Francoise