Re: kern.maxpipekva exceeded, please see tuning(7).

From: Josef Karthauser <joe_at_FreeBSD.org>
Date: Wed, 4 Aug 2004 11:57:00 +0100
On Wed, Aug 04, 2004 at 10:52:12AM +0100, Dick Davies wrote:
> * Josef Karthauser <joe_at_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_at_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 tried
> to build a port .... O_o
> 
> any chance you changed something similar in your networking?
> (maybe a loop in your NAT rules or something?)

The problem appears to be caused by a failing disk returning DMA
errors in swap space.  What probably happened is that the tcp
connections stacked up and blew the alloted space.

Joe
-- 
Josef Karthauser (joe_at_tao.org.uk)	       http://www.josef-k.net/
FreeBSD (cvs meister, admin and hacker)     http://www.uk.FreeBSD.org/
Physics Particle Theory (student)   http://www.pact.cpes.sussex.ac.uk/
================ An eclectic mix of fact and theory. =================

Received on Wed Aug 04 2004 - 08:57:23 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:04 UTC