I believe Shawn is running Windows.  In any case, typically this kind of crash means that LISTSERV ran out of process memory and crashed as a result (although under Windows, usually I would expect to see a HeapAlloc() error right before the crash).  The last 100 or so entries in the log before the crash should give you an idea what LISTSERV was doing when it crashed, and the support group should be able to help you figure out what caused it.

Nathan

At 11:44 AM 2/26/2007 -0500, you wrote:
>Used to happen to me fairly often, so I now run a job every 15 minutes to make sure the server is running and if it is not I restart it.  We are running AIX.
>
>At 10:28 AM -0600 2/26/07, Harpe, Shawn wrote:
>>Has anyone experienced this problem where the Listserv service just
>>stops?  I have seen nothing in the logs except that it terminated
>>unexpectedly.
>>
>>
>>
>>Shawn Harpe
>
>
>-- 
>What do you call a fish with no eyes? A fsh.
>
>Bill Verity - 814-865-4758  Fax: 814-863-7049
>215A Computer Building - Information Technology Services, Penn State University
>At the office - on my Mac, of course ;-)