Date: Mon, 10 Jan 2000 18:25:41 -0800 From: "Scott Hess" <scott@avantgo.com> To: "Fabian Thylmann" <fthylmann@stats.net>, <questions@freebsd.org> Subject: Re: Problem with not disappearing sockets. Message-ID: <1c6301bf5bdb$2810d360$1e80000a@avantgo.com> References: <004301bf58c6$9f33bc40$0593e289@oph.rwthaachen.de> <0ad901bf587b$6fde13f0$1e80000a@avantgo.com> <002a01bf5c26$a4227ee0$0593e289@oih.rwthaachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Fabian Thylmann <fthylmann@stats.net> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1c6301bf5bdb$2810d360$1e80000a>