Date: Wed, 23 Oct 2002 20:39:20 -0700 From: Kevin Stevens <Kevin_Stevens@pursued-with.net> To: Don Bowman <don@sandvine.com> Cc: "'freebsd-net@freebsd.org'" <freebsd-net@FreeBSD.ORG> Subject: Re: Machine becomes non-responsive, only ^T shows it as alive under l oad: IPFW, TCP proxying Message-ID: <2E426952-E702-11D6-B91F-003065715DA8@pursued-with.net> In-Reply-To: <FE045D4D9F7AED4CBFF1B3B813C8533701022D4F@mail.sandvine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, Oct 23, 2002, at 19:41 US/Pacific, Don Bowman wrote: > I have an application listening on an ipfw 'fwd' rule. > I'm sending ~3K new sessions per second to it. It > has to turn around and issue some of these out as > a proxy, in response to which some of them the destination > host won't exist. > > I have RST limiting on. I'm seeing messages like: > Limiting open port RST response from 1312 to 200 packets per second > > come out sometimes. > > After a while of such operation (~1/2 hour), the machine > becomes unresponsive: the network interfaces no longer respond, > the serial console responds to ^T yielding a status line, > but ^C etc do nothing, and the bash which was there won't > give me a prompt. > > ^T indicates my bash is running, 0% of CPU in use, etc. > > I have no choice but to power-cycle it. > > Any suggestions for how one would start debugging this to > find out where its stuck, and how? At a guess, you need to tune the state-table retention time down. KeS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2E426952-E702-11D6-B91F-003065715DA8>