Re: 6.1: kern.ipc.maxpipekva
On Sat, 17 Jun 2006, 16:44-0300, Marc G. Fournier wrote: > > Jun 17 16:00:03 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) > Jun 17 16:00:04 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) I thought about removing this reference but then decided that better to add a couple of words to tuning(7) man page (and didn't add). > but I can't seem to find anything in tuning(7) about it ... so, what > is it and how do I monitor for it? kern/sys_pipe.c: * In order to limit the resource use of pipes, two sysctls exist: * * kern.ipc.maxpipekva - This is a hard limit on the amount of pageable * address space available to us in pipe_map. This value is normally * autotuned, but may also be loader tuned. * * kern.ipc.pipekva - This read-only sysctl tracks the current amount of * memory in use by pipes. -- Maxim Konovalov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1: kern.ipc.maxpipekva
On Sat, 17 Jun 2006, Marc G. Fournier wrote: Jun 17 16:00:03 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) Jun 17 16:00:04 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) but I can't seem to find anything in tuning(7) about it ... so, what is it and how do I monitor for it? More on this: # sysctl -a | grep pipekva kern.ipc.maxpipekva: 16777216 kern.ipc.pipekva: 15122432 and I just rebooted the server ... so obviously I've been living on the edge ... not sure what to increase it to, since not sure what it affects, so will wait on responses ... thx Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1: kern.ipc.maxpipekva
In the last episode (Jun 17), Marc G. Fournier said: > On Sat, 17 Jun 2006, Marc G. Fournier wrote: > >Jun 17 16:00:03 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) > >Jun 17 16:00:04 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) > > > >but I can't seem to find anything in tuning(7) about it ... so, what > >is it and how do I monitor for it? > > More on this: > > # sysctl -a | grep pipekva > kern.ipc.maxpipekva: 16777216 > kern.ipc.pipekva: 15122432 > > and I just rebooted the server ... > > so obviously I've been living on the edge ... not sure what to increase it > to, since not sure what it affects, so will wait on responses ... Try also running "sysctl kern.ipc | grep pipe", which will also tell you how many pipes are in use, plus some other counters. The comment at the top of sys/kern/sys_pipe.c explains how pipes are given memory. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1: kern.ipc.maxpipekva
Great, I just kill'd the server .. I added: kern.ipc.maxpipekva=25165824 to /boot/loader.conf, to give an extra 8M to the PIPE KVA ... then rebooted, and it didn't come back up ... its a remote server, so am waiting for a tech right now to look at it, but ... Is there something else I should be doing? :( On Sat, 17 Jun 2006, Marc G. Fournier wrote: On Sat, 17 Jun 2006, Marc G. Fournier wrote: Jun 17 16:00:03 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) Jun 17 16:00:04 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) but I can't seem to find anything in tuning(7) about it ... so, what is it and how do I monitor for it? More on this: # sysctl -a | grep pipekva kern.ipc.maxpipekva: 16777216 kern.ipc.pipekva: 15122432 and I just rebooted the server ... so obviously I've been living on the edge ... not sure what to increase it to, since not sure what it affects, so will wait on responses ... thx Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1: kern.ipc.maxpipekva
On Sat, 17 Jun 2006, Maxim Konovalov wrote: On Sat, 17 Jun 2006, 16:44-0300, Marc G. Fournier wrote: Jun 17 16:00:03 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) Jun 17 16:00:04 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) I thought about removing this reference but then decided that better to add a couple of words to tuning(7) man page (and didn't add). but I can't seem to find anything in tuning(7) about it ... so, what is it and how do I monitor for it? kern/sys_pipe.c: * In order to limit the resource use of pipes, two sysctls exist: * * kern.ipc.maxpipekva - This is a hard limit on the amount of pageable * address space available to us in pipe_map. This value is normally * autotuned, but may also be loader tuned. * * kern.ipc.pipekva - This read-only sysctl tracks the current amount of * memory in use by pipes. See my other note, but I take it just adding: kern.ipc.maxpipekva=25165824 and reboot is the wrong thing to do, since the server didn't come back :( Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1: kern.ipc.maxpipekva
On Sat, 17 Jun 2006, 17:23-0300, Marc G. Fournier wrote: > On Sat, 17 Jun 2006, Maxim Konovalov wrote: > > > On Sat, 17 Jun 2006, 16:44-0300, Marc G. Fournier wrote: > > > > > > > > Jun 17 16:00:03 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) > > > Jun 17 16:00:04 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) > > > > I thought about removing this reference but then decided that better > > to add a couple of words to tuning(7) man page (and didn't add). > > > > > but I can't seem to find anything in tuning(7) about it ... so, what > > > is it and how do I monitor for it? > > > > kern/sys_pipe.c: > > > > * In order to limit the resource use of pipes, two sysctls exist: > > * > > * kern.ipc.maxpipekva - This is a hard limit on the amount of pageable > > * address space available to us in pipe_map. This value is normally > > * autotuned, but may also be loader tuned. > > * > > * kern.ipc.pipekva - This read-only sysctl tracks the current amount of > > * memory in use by pipes. > > See my other note, but I take it just adding: > > kern.ipc.maxpipekva=25165824 > > and reboot is the wrong thing to do, since the server didn't come back :( Increase KVA_PAGES, see /sys/i386/conf/NOTES for details. -- Maxim Konovalov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1: kern.ipc.maxpipekva
On Sat, 17 Jun 2006, Dan Nelson wrote: In the last episode (Jun 17), Marc G. Fournier said: On Sat, 17 Jun 2006, Marc G. Fournier wrote: Jun 17 16:00:03 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) Jun 17 16:00:04 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) but I can't seem to find anything in tuning(7) about it ... so, what is it and how do I monitor for it? More on this: # sysctl -a | grep pipekva kern.ipc.maxpipekva: 16777216 kern.ipc.pipekva: 15122432 and I just rebooted the server ... so obviously I've been living on the edge ... not sure what to increase it to, since not sure what it affects, so will wait on responses ... Try also running "sysctl kern.ipc | grep pipe", which will also tell you how many pipes are in use, plus some other counters. The comment at the top of sys/kern/sys_pipe.c explains how pipes are given memory. What uses all of these pipes? right now, with 97 jails running: kern.ipc.maxpipekva: 25165824 kern.ipc.pipes: 7038 kern.ipc.pipekva: 22179840 kern.ipc.pipefragretry: 0 kern.ipc.pipeallocfail: 0 kern.ipc.piperesizefail: 0 kern.ipc.piperesizeallowed: 1 That is an average of 7 pipes per process: pluto# ps aux | wc -l 1326 Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1: kern.ipc.maxpipekva
In the last episode (Jun 17), Marc G. Fournier said: > On Sat, 17 Jun 2006, Dan Nelson wrote: > >In the last episode (Jun 17), Marc G. Fournier said: > >>On Sat, 17 Jun 2006, Marc G. Fournier wrote: > >>>Jun 17 16:00:03 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) > >>>Jun 17 16:00:04 pluto kernel: kern.ipc.maxpipekva exceeded; see tuning(7) > >>> > >>>but I can't seem to find anything in tuning(7) about it ... so, > >>>what is it and how do I monitor for it? > >> > >>More on this: > >> > >># sysctl -a | grep pipekva > >>kern.ipc.maxpipekva: 16777216 > >>kern.ipc.pipekva: 15122432 > >> > >>and I just rebooted the server ... > >> > >>so obviously I've been living on the edge ... not sure what to > >>increase it to, since not sure what it affects, so will wait on > >>responses ... > > > >Try also running "sysctl kern.ipc | grep pipe", which will also tell > >you how many pipes are in use, plus some other counters. The > >comment at the top of sys/kern/sys_pipe.c explains how pipes are > >given memory. > > What uses all of these pipes? right now, with 97 jails running: > > kern.ipc.maxpipekva: 25165824 > kern.ipc.pipes: 7038 > kern.ipc.pipekva: 22179840 > kern.ipc.pipefragretry: 0 > kern.ipc.pipeallocfail: 0 > kern.ipc.piperesizefail: 0 > kern.ipc.piperesizeallowed: 1 > > That is an average of 7 pipes per process: > > pluto# ps aux | wc -l > 1326 "fstat | grep pipe" will tell you what processes have them open on what fds. pipes on fds 0, 1 and 2 are probably from shell pipelines. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1: kern.ipc.maxpipekva
On Sat, 17 Jun 2006, Dan Nelson wrote:
"fstat | grep pipe" will tell you what processes have them open on what
fds. pipes on fds 0, 1 and 2 are probably from shell pipelines.
Yowch, everything uses a pipe ... most of it is postfix related stuff,
mind you ...
pluto# fstat | grep pipe | awk '{print $2}' | sort -u
anvil
cleanup
csh
flush
fstat
grep
httpd
imapd
inetd
java
lmtp
lmtpd
local
master
nsd
perl5.8.8
php
pickup
pop3d
proxymap
qmgr
sh
smtp
smtpd
sshd
trivial-rewrite
pluto# fstat | grep pipe | awk '{print $2}' | wc -l
8707
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED]
Yahoo . yscrappy Skype: hub.orgICQ . 7615664
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
