From owner-freebsd-hackers Tue Sep 14 16:45:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id B9B4D14D51 for ; Tue, 14 Sep 1999 16:45:50 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1003) id 8A26CF817; Tue, 14 Sep 1999 19:45:48 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 7C4879B17; Tue, 14 Sep 1999 19:45:48 -0400 (EDT) Date: Tue, 14 Sep 1999 19:45:48 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: Stevan Arychuk Cc: hackers@freebsd.org Subject: Re: help with flaky reboot on 3.1 In-Reply-To: <37DEDD59.6FFDFEAD@avantgo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Sep 1999, Stevan Arychuk wrote: > Greetings, > > We are running 3.1-RELEASE with a kernel pulled on May 1, 1999 from the > RELENG_3 branch (used this to take advantage of the KVA modifications > that were rolled in after the release). > > > Here are the symptoms we are seeing: > > 1 machine running a caching squid reverse proxy would spontaneously > reboot with no error messages every week or so. This machine was a > single CPU only. > > We were seeing an excessive number of sockets in the CLOSING state, via > netstat. The reboots seemed to be co-related to having many such > sockets. Suspecting bad TCP stack on the Internet, we did 'sysctl -w > net.inet.tcp.always_keepalive=1' This fixed the many CLOSING sockets > problem, but did not fix the reboots. > > Other machines running custom software (Dual CPU) would also > spontaneously reboot also with no error messages. The reboots are > happening on an increasing frequency, almost to the point of a couple > times a day. Sometimes a machine would reboot a couple times a day, > then be ok for another week or so. > > Our software excercies the disk, CPU and network quite a bit, but not > excessively. The only machines that are having problems, are production > machines directly connected to the Internet. We've had the same > machines running internally with longer uptimes, and heavier volumes. > > Any suggestions/idea's? > > Sorry about the super-post, I thought detail was important. > > - Stevan Arychuk > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message