Folks ...

This has been posted twice before and I have no resolution or way to
proceed.  Can someone explain what I should do?  I've already corresponded
with the listmaster at some length on this issue and (Kary, correct me if
I'm wrong here) neither of us knows what to do to make it better.

Is there a different or better route I can use to contact LSoft for
support?  I don't want to abuse this list or repeat the issue again, but I
still have archives intermittently down and at least one list member who
doesn't get why there is no answer as to what might be done about this (he
doesn't expect a quick fix, just wonders if anybody cares).

I did see, in response to my first post, Nathan's comment that the message
means the file doesn't exist.  I get that, but we have no clue why the
file for the current month's archives sometimes seems to exist and
sometimes doesn't (I don't know that it's ever really gone, but the web
interface thinks it is).

Thanks.

Tom

================================================================

I have a user who reports that the archives for the current month go down
frequently at mid-day and don't come back up until late at night.  "Down"
means any attempt to access them via the web comes up with a standard
error:

>    Error – cannot access archive files
>
>    The archive files could not be accessed, probably because they are
>    being updated. Please try again in about 30 seconds, and report the
>    problem if it persists for more than a few minutes. The file that
>    could not be opened is
>    'RAID2:[WWW-ARCHIVES.guatemala-adopt]guatemala-adopt.ind0005' and the
>    error code was  2.

Despite the message, the problem does not go away in a few minutes -- it
takes hours (presumably until a scheduled late-night restart cycle).

At one point the problem went away for a while when the site manager
reindexed the file in question, but it came back.

One other list owner at the same site (SJU) reports the same problem.

What can we do, or what can the site manager do, to solve this?  Is it any
kind of known bug in LISTSERV, or in the web interface?

Thanks.


-----
Tom Rawson           [log in to unmask]