From owner-freebsd-stable Fri Mar 17 9:29:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 37D2D37BEFD for ; Fri, 17 Mar 2000 09:29:12 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 12W0Yg-0002Bx-00; Fri, 17 Mar 2000 09:29:10 -0800 Date: Fri, 17 Mar 2000 09:29:08 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Michael Robinson Cc: freebsd-stable@freebsd.org Subject: Re: How to force remote reboot of 3.4-Release? In-Reply-To: <200003170213.KAA26062@netrinsics.com> 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 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