Date: Mon, 11 Apr 2011 11:19:41 +0700 From: Eugene Grosbein <egrosbein@rdtc.ru> To: Przemyslaw Frasunek <przemyslaw@frasunek.com> Cc: freebsd-net@freebsd.org Subject: Re: mpd5/Netgraph issues after upgrading to 7.4 Message-ID: <4DA2815D.3090807@rdtc.ru> In-Reply-To: <4DA23090.8060206@frasunek.com> References: <4D947756.6050808@freebsd.lublin.pl> <4D9F6C71.1040209@frasunek.com> <4DA171BA.9000507@frasunek.com> <4DA1E39C.9090300@rdtc.ru> <4DA23090.8060206@frasunek.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11.04.2011 05:34, Przemyslaw Frasunek wrote: >> Use command "vmstat -z|egrep 'ITEM|NetGraph'" and check FAILURES column. >> If you see non-zero values there, you need to increase netgraph memory limits >> net.graph.maxdata and net.graph.maxalloc using /boot/loader.conf. > > Unfortunately, increasing net.graph.maxdata & net.graph.maxalloc didn't > solved EPERM problems on netgraph control sockets. It is still appearing > every few hours, but failure counters are zero: > > ITEM SIZE LIMIT USED FREE REQUESTS > FAILURES > NetGraph items: 36, 65598, 0, 1404, 52978, > 0 > NetGraph data items: 36, 65598, 0, 780, 2876420, > 0 > > I also tried to increase kern.ipc.nmbclusters to 262140, but after that, > mpd stopped accepting any connections - each failed with ENOBUFS. > > What is the upper limit of kernel memory usage? It depends on your FreeBSD version (arch is significant too) and physical RAM size. Eugene Grosbein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DA2815D.3090807>