From owner-freebsd-questions Thu Oct 10 4:34:51 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFA9937B401 for ; Thu, 10 Oct 2002 04:34:49 -0700 (PDT) Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id E935E43E91 for ; Thu, 10 Oct 2002 04:34:48 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [IPv6:::1]) by lurza.secnetix.de (8.12.5/8.12.5) with ESMTP id g9ABYlmC045168 for ; Thu, 10 Oct 2002 13:34:47 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.12.5/8.12.5/Submit) id g9ABYlTF045167; Thu, 10 Oct 2002 13:34:47 +0200 (CEST) Date: Thu, 10 Oct 2002 13:34:47 +0200 (CEST) Message-Id: <200210101134.g9ABYlTF045167@lurza.secnetix.de> From: Oliver Fromme To: freebsd-questions@FreeBSD.ORG Reply-To: freebsd-questions@FreeBSD.ORG Subject: Re: file table is full In-Reply-To: <20021010055139.B84195@freeze.org> X-Newsgroups: list.freebsd-questions User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.6-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jim Freeze wrote: > rabbit kernel log messages: > > 246:3175 63.106.140.204:22 in via sis0 > > file: table is full There is a limit on the number of files than can be held open simultaneously. If that limit is reached, the above message is logged, and trying to open further files will fail. What value do you have for "maxusers" in your kernel? The default ("0") is to adapt it to the amount of memory, but maybe you should set it to a higher value. > > Limiting open port RST response from 250 to 200 packets per second This looks like someone was portscanning you, or _maybe_ some kind of DoS attack. In that case, the kernel auto- matically decreases the rate at which it responds to such network packets, so the scan or attack does not have a big impact on regular system performance. > > pmap_collect: collecting pv entries -- suggest increasing PMAP_SHPGPERPROC This can happen if you have programs that make extensive use of shared memory. I'd suggest you try what the message says and increase the value of PMAP_SHPGPERPROC in your kernel. The default is 200, I think. You could try 400 for a start (don't set it too high, or you might run out of kernel VM space!). > The only thing that I can think that caused this is that I was > running the apache benchmark ab with 1000 tests and 50 concurrent > accessors.. That sounds like an explanation. > Is there a direct way to see if this problem is gone? If there are no more such messages logged. :-) Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message