Date: Fri, 21 Sep 2007 08:04:19 +0200 From: "Claus Guttesen" <kometen@gmail.com> To: "Borja Marcos" <BORJAMAR@sarenet.es> Cc: freebsd-current@freebsd.org Subject: Re: Memory allocation problems (ZFS/NFS/amd64) Message-ID: <b41c75520709202304j11005fcw2c849d66c4d63294@mail.gmail.com> In-Reply-To: <4C4A3C06-A6F3-41B1-BE53-F04369CD4F8D@SARENET.ES> References: <5870F83F-7174-47AA-98AE-C1DE8972E0C8@SARENET.ES> <fcrmmp$2ug$1@sea.gmane.org> <613318C3-6B66-4758-A0D4-97405D6A1914@SARENET.ES> <46F23166.8070908@FreeBSD.org> <A9B46B5C-F44F-4A1B-8989-E0E7CAA70BFA@SARENET.ES> <F59EF073-57D8-429E-8F6C-B702AFD8B732@SARENET.ES> <4C4A3C06-A6F3-41B1-BE53-F04369CD4F8D@SARENET.ES>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I've just tried using the echo service from inetd, and the server > > is keeping 1024 established > > connections without that error. I just don't understand why this > > can fail with Apache, but it seems it's an issue with -current, as > > we have a similar setup with 6.2(i386), same hardware, and it works. > > Here's what I've found out. Apache was confgured by a different > person, and I didn't notice that the MaxClients parameter was set too > low (159). > > Setting it up to a high value (1024) has made those errors disappear. > So that "memory limit" was actually that the system was dropping > connection requests from the listen queue. The error message is quite > looks misleading to me. At least I had never seen it, so it caught me > by surprise. Thank you. I was planning to upgrade our file/samba server with current from June 11'th next week to get the latest enhancements related to zfs. And with 5 TB in use the last thing I needed was dropped connections. :-) -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b41c75520709202304j11005fcw2c849d66c4d63294>