From owner-freebsd-stable Fri Mar 17 13:55: 1 2000 Delivered-To: freebsd-stable@freebsd.org Received: from boris.netgate.net (boris.netgate.net [204.145.147.154]) by hub.freebsd.org (Postfix) with ESMTP id 5171E37B6CD for ; Fri, 17 Mar 2000 13:54:58 -0800 (PST) (envelope-from fbsddave@mrcaffeine.com) Received: from localhost (wellsian@localhost) by boris.netgate.net (8.9.3/8.9.3) with ESMTP id NAA50609; Fri, 17 Mar 2000 13:51:42 -0800 (PST) (envelope-from fbsddave@mrcaffeine.com) Date: Fri, 17 Mar 2000 13:51:42 -0800 (PST) From: fbsd-dave X-Sender: wellsian@boris.netgate.net To: Michael Robinson Cc: freebsd-stable@FreeBSD.ORG Subject: Re: How to force remote reboot of 3.4-Release? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Have you considered a remote power control device? Like: http://www.baytechdcd.com/ http://www.apcc.com/products/pdu.cfm Dave On Fri, 17 Mar 2000, Tom wrote: > On Fri, 17 Mar 2000, Michael Robinson wrote: > > > Last night, I was running a very large Postgresql query on one of my > > colocated development servers when all of a sudden the session completely > > froze. Since then, I can get TCP connections to all the open ports, but > > they just hang with no services ever coming up. Ping works fine. > > > > I assume this is due to one of FreeBSD's resource starvation features. > > What I'd like to know is, once the server gets into this state, is it > > possible to exploit any of the other resource starvation features in > > 3.4-Release to force a reboot? Getting access to the server is a big > > pain in the rear, so I'd like to avoid the trip if at all possible. > > > > Would a SYN flood do it? If so, does anyone know of a good SYN flood tool? > > > > -Michael Robinson > > It sounds like a disk hang actually. If you had access to the console > you'd probably see various disk warnings/errors. > > There are no known remote reboot exploits. > > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message