OK, here's one I'm not sure how to handle, one of our list-owners complained
that their list is held and cannot be freed, so I tried to free it for
them, and it gets held again. I moved the digest out of the way, and freed
the list, and all queued messages left the spool, were distributed to the
list, and were put in the digest. After that list was freed, I set the
digest limit to just above the current digest size and another message came
in, here is what happened:
All names except for mine changed for their protection, the log shows:
13 Mar 2000 12:23:07 Processing mail from [log in to unmask] for THE_LIST
*** FIO file cache now totals 4632k. A list of cached files follows. ***
File size Usage Flags File name
--------- ----- ----- ---------
3043k 1 U /archives/the_list/the_list.log00
5k 3 /export/home/listserv/home/the_list.list
19k 1 /export/home/listserv/tmp/listserv.cmsut1
501k 1 /export/home/listserv/home/signup.file5
39k 10 K /export/home/listserv/home/default.mailtpl
12k 7 /export/home/listserv/home/service.names
3k 2 /export/home/listserv/home/digests.file
*** FIO file cache now totals 4106k. A list of cached files follows. ***
File size Usage Flags File name
--------- ----- ----- ---------
1042k 1 U /archives/the_list/the_list.digest
3k 1 /export/home/listserv/home/digests.file
3062k 1 /archives/the_list/the_list.log00
13 Mar 2000 12:23:07 Digest size limit exceeded, sending special issue...
13 Mar 2000 12:23:07 To [log in to unmask]: An error occurred while logging mail
to the archives of the THE_LIST (...)
13 Mar 2000 12:23:07 To [log in to unmask]: An error occurred while logging m
ail to the archives of the THE_LIST (...)
And the "relevant" parts of the header look like:
% listview home/the_list | egrep -i digest\|notebook
* NOTEBOOK = yes,/archives/the_list,yearly,private
* DIGEST = yes,same,daily,,Size(13600)
% wc -l the_list.digest
13576 the_list.digest
% ls -l /var/spool/listserv/*the_list*
-rw-r--r-- 1 listserv other 16905 Mar 13 12:21 /spool/listserv/3532439_15_the_list.jobh
% jobview /spool/listserv/3532439_15_the_list.jobh | wc -l
343
% wc -l the_list.digest
13914 the_list.digest
And, the message _did_ get appended to the the_list.digest, but did not get
distributed normally, nor did the digest get distributed. We and the owners
then received yet another:
Subject: Message ("An error occurred while logging mail to the...")
An error occurred while logging mail to the archives of the THE_LIST
list. An incomplete copy of the message might be present in the archive
file. The list is being held to prevent further occurrences of this error.
Please take corrective action and issue a "FREE THE_LIST" command
when you want the message to be reprocessed.
message. If I FREE the list, the held message gets appended to the digest
file _again_ with a repeat of the above message, yet the message is still
spooled without being delivered, and the digest remains undelivered.
Any assistance would be appreciated.
Thank you,
philip
--
Philip Kizer <[log in to unmask]>
Texas A&M CIS Operating Systems Group, Unix
|
