Hello,

It turned out that particular digest and (troubled-list).log1102d were
corrupted.  ListServ resumed normal operation after removed those two files.

Shinn

On 2/25/2011 2:34 AM, Shinn Wu wrote:
> Hello,
>
> We just upgraded to 16.0 last year.  One of our old lists (have been
> running several years) suddenly stopped working with the log:
>
> (trouble-list)  digest (regular) is being distributed...
>
> it blocked distributions of all other lists.  lsv used 100% CPU.  I
> moved  ~spool, ~tmp to other directories, removed
> (troubled-list).db*.  Restarted listserv (several times), ListServ
> reindex the (troubled-list) and then stopped at the same place (which
> showed above).  Mail log showed:
>
> Feb 25 02:28:54 newlists sendmail[7693]: [ID 801593 mail.info]
> p1PASsrY007693: to=<[log in to unmask]>,
> delay=00:00:00, pri=54375, stat=Please try again later
>
> There were lot of *.job in spool directory but ListServ won't process
> them.
>
> My question is: how to remove the digest distribution so other lists
> could normally post.
>
> Thank for your help (it's 2:30AM and I am still awake).
>
> Shinn
>
> ############################
>
> To unsubscribe from the LSTSRV-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=LSTSRV-L&A=1

############################

To unsubscribe from the LSTSRV-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=LSTSRV-L&A=1