Date: Wed, 4 Aug 2004 10:52:12 +0100 From: Dick Davies <rasputnik@hellooperator.net> To: Josef Karthauser <joe@FreeBSD.org> Cc: FreeBSD Current list <freebsd-current@freebsd.org> Subject: Re: kern.maxpipekva exceeded, please see tuning(7). Message-ID: <20040804095212.GC13269@lb.tenfour> In-Reply-To: <20040804091722.GB5782@genius.tao.org.uk> References: <20040804091722.GB5782@genius.tao.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
* Josef Karthauser <joe@FreeBSD.org> [0818 10:18]: > I've got a 5.2.x machine which has hung and is giving the message > 'kern.maxpipekva exceeded, please see tuning(7)' on the console > whenever anyone tries to open a tcp connect to it. Does anyone > know what this tweakable is about and what might cause it to be > "exceeded"? The machine has been running fine for 6 months. It's a typo, should be: root@eris samba3 # sysctl -a|grep kva kern.ipc.maxpipekva: 8359936 kern.ipc.maxpipekvawired: 4177920 kern.ipc.pipekva: 262144 kern.ipc.pipekvawired: 0 vfs.buffreekvacnt: 0 - when I had this a oouple of weeks back (on 5.2 release) it was because I'd borked my make.conf so I effectively forkbombed the box everytime I tri= ed to build a port .... O_o any chance you changed something similar in your networking? (maybe a loop in your NAT rules or something?) --=20 An artist should be fit for the best society and keep out of it. Rasputin :: Jack of All Trades - Master of Nuns
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040804095212.GC13269>