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 majord...@freebsd.org > with "unsubscribe freebsd-hackers" in the body of the message >
----- Chris D. Faulhaber <jed...@fxp.org> | 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 majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
