Several sites have reported this problem,  all of them large servers with
lots of  lists. The  most probable  cause for this  behaviour is  lack of
virtual  storage. Are  all  the  usual digests  being  processed, or  did
LISTSERV stop mid-way in  the list of digests to process?  At any rate, I
suggest  increasing virtual  storage to  32M and  switching to  an XA/ESA
virtual  machine. This  should increase  the amount  of storage  actually
available to LISTSERV to 10M. Sites  with a maintenance contract can also
install the XA-exploitive version of LISTSERV.
 
  Eric