The following reply was made to PR os-linux/3343; it has been noted by GNATS.
From: Mark <[EMAIL PROTECTED]> To: Marc Slemko <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: os-linux/3343: Server dies after 1-20 hours of usage. Date: Mon, 09 Nov 1998 21:34:07 +0000 Marc Slemko wrote: > On 6 Nov 1998, Mark wrote: > > > The following reply was made to PR os-linux/3343; it has been noted by > > GNATS. > > > > From: Mark <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED] > > Subject: Re: os-linux/3343: Server dies after 1-20 hours of usage. > > Date: Fri, 06 Nov 1998 21:36:06 +0000 > > > > [EMAIL PROTECTED] wrote: > > > > > [In order for any reply to be added to the PR database, ] > > > [you need to include <[EMAIL PROTECTED]> in the Cc line ] > > > [and leave the subject line UNCHANGED. This is not done] > > > [automatically because of the potential for mail loops. ] > > > [If you do not include this Cc, your reply may be ig- ] > > > [nored unless you are responding to an explicit request ] > > > [from a developer. ] > > > [Reply only with text; DO NOT SEND ATTACHMENTS! ] > > > > > > Synopsis: Server dies after 1-20 hours of usage. > > > > > > Comment-Added-By: lars > > > Comment-Added-When: Fri Nov 6 10:26:46 PST 1998 > > > Comment-Added: > > > > > > Are you using NFS? > > > Any third party modules? > > > > No. NFS is disabled, and we did not compile any 3rd party modules into > > the server. The only extra module that I enabled was the status > > module. The server ran fine for about 6 months before this started. Is > > there anything in the OS itself that may have changed to cause this > > problem? > > Did you upgrade your kernel version or any libraries, especially libc > around when it started happening? No, we did not make any such changes to the machine since the end of Septemper. This problem started well afterwards. It is a friend's machine, and he did tell me one thing that is interesting about this problem: it seems to be happening consistently between 6:30am and 8:30am CST. We checked for cron jobs running at this time, and we didn't find any. Are there any new attacks against the server that you know of that could cause this behavior?
