From owner-freebsd-stable Mon Sep 27 10:18: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id E385215240 for ; Mon, 27 Sep 1999 10:18:03 -0700 (PDT) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.3/8.9.1) id NAA40833 for stable@freebsd.org; Mon, 27 Sep 1999 13:18:01 -0400 (EDT) (envelope-from mi) Message-Id: <199909271718.NAA40833@misha.cisco.com> Subject: Re: nmap V. 2.3BETA5 causes panic In-Reply-To: <4.2.0.58.19990927032147.00a3d680@mail.elcjn1.sdca.home.com> from Bryan Talbot at "Sep 27, 1999 03:28:29 am" To: stable@freebsd.org Date: Mon, 27 Sep 1999 13:18:01 -0400 (EDT) Reply-To: mi@aldan.algebra.com From: Mikhail Teterin X-Mailer: ELM [version 2.4ME+ PL60 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bryan Talbot once wrote: > At 02:43 AM 9/27/99 , Andy Farkas wrote: > >The system will panic with an 'out of mbufs' message when I run the > >above nmap command ("ping scan" a class B subnet - my internal IP > >network). > I'm no expert but this basic question has been asked many times on > this list recently. It seems to be a known problem that FreeBSD > currently panics if it runs out of mbufs. We all wish this wasn't so > and maybe someday it won't be. Actually, there are systems out there where this is NOT so. I would not be so tactless to point it out, but it is FreeBSD-2.2*. Once, after 3 monthes of uptime, I tried to simulate an "attack" on my (colocated) web-server -- a humble P100 with 32Mb of RAM on 100Mb network -- by issuing numerous fetch-requests from a machine nearby. The requests where steadily growing in number and in a couple of minutes the server locked up. I was preparing to call the ISP (Ziplink) to ask them to reboot it, but it unlocked in about 40 seconds. There were "out of mbuf" messages in the log, but it stayed up for over 10 more monthes (!) until finaly its IDE disk started to glitch. And that was not even the 2.2.x-RELEASE or anything, but some sort of 2.2-BETA or something. Too bad out current ISP (9NetAve) has some sorts of mistery problem (I suspect some dummy just trips over the power cables once in a while), so I cannot get over 3 monthes of uptime from the our new 2.2.8 machine. Or is this a different type of "out of mbuf..."? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message