Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Mar 2000 09:29:08 -0800 (PST)
From:      Tom <tom@uniserve.com>
To:        Michael Robinson <robinson@netrinsics.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: How to force remote reboot of 3.4-Release?
Message-ID:  <Pine.BSF.4.05.10003170927530.19874-100000@shell.uniserve.ca>
In-Reply-To: <200003170213.KAA26062@netrinsics.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.10003170927530.19874-100000>