From owner-freebsd-questions Mon Jan 10 18:26:38 2000 Delivered-To: freebsd-questions@freebsd.org Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194]) by hub.freebsd.org (Postfix) with ESMTP id 2A6B214DEB for ; Mon, 10 Jan 2000 18:26:34 -0800 (PST) (envelope-from scott@avantgo.com) Received: from river ([10.0.128.30]) by bomber.avantgo.com (Netscape Messaging Server 3.5) with SMTP id 368; Mon, 10 Jan 2000 18:23:02 -0800 Message-ID: <1c6301bf5bdb$2810d360$1e80000a@avantgo.com> From: "Scott Hess" To: "Fabian Thylmann" , References: <004301bf58c6$9f33bc40$0593e289@oph.rwthaachen.de> <0ad901bf587b$6fde13f0$1e80000a@avantgo.com> <002a01bf5c26$a4227ee0$0593e289@oih.rwthaachen.de> Subject: Re: Problem with not disappearing sockets. Date: Mon, 10 Jan 2000 18:25:41 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fabian Thylmann > The way we handle the high socket numbers is just a very high maxusers > setting in the kernel and on top of that also directly setting the max > nmbclusters to a high number (even higher than the calculated one that > results from the maxusers) ..... This helped keeping the box from kernel > panicing because of mbuf cluster overruns, which I guess your box probably > crashes on. Check the netstat -m numbers, that will give you info on max and > current mbuf usage. If thats very close, its probably mbuf clusters running > out and the kernel panicing on that. > The easiest way to get around this is to just increase the maxusers number > in the kernel. Hmm, must be something else, then. Our MAXUSERS is set to 512, and our nmbclusters is set obscenely high, 33280. netstat -m reports seldom get above 20%. Later, scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message