Rick Narad wrote:
> This is the second time that this has occured recently.
This is because the problem wasn't solved the first time. Let's try to
analyze the error below.
> I'm sending commands with email.
No problem.
> I sent the "free" command and one file was released but there was no
> indication if this fixed the actual problem.
It didn't.
> Everytime I think I've got listowning down, it throws me a new one. :-)
Don't worry about it--I'm still learning, myself. We're on this list
because we all are :) Don't let the fact that I'm trying to write a primer
for LISTSERV fool you in to thinking I know everything about it.
And now for the dissection:
> =========================original message===================================
> From: IN%"[log in to unmask]"
> Subj: Message ("An error occurred while logging mail to the...")
>
> An error occurred while logging mail to the archives of the HEALTHRE list.
> An incomplete copy of the message might be present in the archive file.
Sneaking a peek ahead of this part of the message will clarify what these
two sentences are describing: a lack of disk space available to store the
mail being written into the message archives.
When you or the other list owner tried to "fix" this before, all you did was
to postpone the inevitable. You still lack sufficient disk space to store
logs of messages to the HEALTHRE list.
> The list is being held to prevent further occurrences of this error.
This is LISTSERV's version of a driver's side airbag. It's preventing
itself from doing itself any more harm.
> Please take corrective action and issue a "FREE HEALTHRE" command when you
> want the message to be reprocessed.
The crucial step is the corrective action you must take before allowing
LISTSERV to drive HEALTHRE into another brick wall. See below.
> Serious error occurred - traceback follows
> ------------------------------------------
> >>> Error X'0010006B' writing file "HEALTHRE LOG9505A G1" <<<
> -> Severity: Error
> -> Facility: FSWRITE
> -> Abstract: Out of disk space
> -> I/O mode: Record write
Yes, as it turns out, your 1st week of May logs are not being written
properly because the supply of disk space your list has been allocated has
run dry.
So what do I do now?
Make disk space available.
How?
Delete any files or message logs you can afford to do away with. Start
deleting the oldest message logs and work your way forward from there. Stop
when you think you have deleted enough to accomodate the disk storage
necessary for the near term message traffic. In the long term, of course,
this problem will recur indefinitely as your list archives reach the limit
of its disk allocation.
How?
Use the PUT command to send one blank file with the name of the oldest
message log. This will cause LISTSERV to delete that log from the archive
and will free up the disk space that it took up for use by logs of future
messages.
What name?
Use the INDEX HEALTHRE command to get a list of the files and message logs
that are stored for the HEALTHRE list. Find the names that have the pattern
HEALTHRE LOGyymmw, where yy == 2-digit year, mm == 2-digit month, w == week
letter (A: 1st-7th, B: 8th-14th, C: 15th-21st, D: 22nd-28th, E: remainder of
month).
What PUT command?
For example, to delete the log for the 1st week of May, 1982, send the
following message (assuming your password is xxxxx):
--------------------------------------------
To: [log in to unmask]
Subject: this is ignored by LISTSERV, anyway
PUT HEALTHRE LOG8205A PW=xxxxx
--------------------------------------------
The dashed lines are only there to show you that you should have nothing
after the PW=xxxxx line. Don't actually type in the rows of dashes! Not
even a blank line should be after the PW=xxxxx line. If possible, try to
make sure the PUT command is the only line in the message text being sent to
LISTSERV.
Repeat with each old log until you feel enough have been deleted to make
room for new messages, then FREE the list. You might want to make backups
of the log files you're affecting, in case you want to access them later.
How do I make backups?
All I really meant was: use the GET command to keep a copy of these for
yourself. I'm the packrat type myself, so I thought I'd mention that.
How do I know it worked?
Try deleting only one message log first. Wait for a message back from
LISTSERV saying the log file was successfully deleted. If not, try again.
The worst that can happen is that the message log file still exists, but has
a vvery short length. When you're confident you have the procedure down
pat, try with the oldest remaining log file, and so on.
Remember, only *one* PUT command per message to LISTSERV.
Good luck!
- Michael; NAUSICAA list owner: <[log in to unmask]>
[ Michael S. Johnson <[log in to unmask]> Computer Science, U of W ]
|
