Tracking down "kern.ipc.maxpipekva exceeded"

Dan Nelson dnelson at allantgroup.com
Thu May 19 10:54:05 PDT 2005


In the last episode (May 19), Ewald Jenisch said:
> > I would suggest keeping an eye on kern.ipc.pipekva and trying to
> > correlate any changes to the activity on the system at the time.
> 
> I've already set this up - and it slowly (over days) is creeping up, e.g.
> 
> May 12 18:00:58 CEST 2005: kern.ipc.pipekva: 114688
> May 19 19:23:29 CEST 2005: kern.ipc.pipekva: 262144
> 
> At least I know what kern.ipc.pipekva is rising but, for me the most
> interesting part is, what actually is using up these resources?

Pipes :)
 
> Is there any chance to get hold of the respective process/program?

lsof | grep PIPE

should do the trick.  Lsof's SIZE/OFF column shows the allocated buffer
size for that pipe.  Most of the time you'll see either 0 (pipe has
never been used) or 16384 (default value).

-- 
	Dan Nelson
	dnelson at allantgroup.com


More information about the freebsd-questions mailing list