On Jun 16, 2006, at 11:20 AM — 6/16/06, Michelle Wilbers wrote:

> One of the first things I tried was removing the larger files from the
> spool, even though none were larger than 50kb. I also tried  
> temporarily
> removing all files older than the time the service stopped, in case  
> one of
> them was corrupt. We virus scanned yesterday and some files from  
> the spool
> and archives were removed because they were infected. Also  
> yesterday we had
> a problem where the drive on which LISTSERV is installed ran out of  
> space.
> This stopped LISTSERV, but once the space problem was resolved, I  
> was able
> to restart LISTSERV without any problems.
>
> I believe the key error code comes from the LISTSERV log, although  
> I cannot
> find an explanation on what it means. I believe Error 8 means,  
> generally, a
> lack of resources:

Allowing your LISTSERV's disk to run out of capacity opens up nasty  
problems. That situation happened to me a few years ago when we run  
LISTSERV 1.8d under Tru64 Unix. I do not recall the specific details  
on how I resolved the issue, but I ended up with some corrupt  
(incomplete) notebooks and I had to write a script to clear out  
cached digest requests.

John Lyon is probably right on target with his recommendation, but if  
what John said does not pan out, I suggest you either open up an  
official support request with L-Soft via email to [log in to unmask]  
or wait for one of the kind L-Soft people to reply to your plea for  
help on this list.

You also should consider installing some system monitoring software  
so that you are alerted when your server's disk grows too full.