On Wed, 20 Nov 2002 12:43:50 PST, "Ahern, Shannon" <[log in to unmask]>  said:
 
> MESSAGE    : The script started from the URL '/archives/wa.exe' with
> parameters 'A1=ind0102c&L=dotnet&D=0&F=P' has not responded within the
> configured timeout period.  The HTTP server is terminating the script.
 
> (sometimes the parameters vary slightly, but always for that list)

I'll place a bet that the list in question has a humongous archive...

> I am wondering if anyone has a clue what this means? I thought maybe
> someone was hitting the box, looking for an archive item with incomplete
> parameters, but the URL actually seems to work if I paste it in.

There's one of two things going on, and the fact it's always the same list
points at one.

1) Most likely - your webserver is configured to terminate a CGI that runs
for more than (for instance) 10 seconds. The list has a big archive, so the
search takes 9.8 seconds (for example) on the average. So when you try, it
happens to finish in time, but other times, system load factors keep it from
finishing until 10.2 seconds have finished - at which point it's been gunned
down by the webserver.

2) wa.exe has to talk to the main 'lsv' process, and sometimes has to wait
for some *previous* task (a large distribute job, etc) to complete, and you
can have timeouts here as well.  I don't think this is the case, since that
would tend to hit requests essentially at random, as they'd depend on what
the *previous* thing Listserv was doing.

Hope that helps...
-- 
                                Valdis Kletnieks
                                Computer Systems Senior Engineer
                                Virginia Tech