From owner-freebsd-questions Thu Aug 22 0:55:43 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 65C3937B400 for ; Thu, 22 Aug 2002 00:55:39 -0700 (PDT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C87643E65 for ; Thu, 22 Aug 2002 00:55:37 -0700 (PDT) (envelope-from Alex.Wilkinson@dsto.defence.gov.au) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.10.1/8.10.1) with ESMTP id g7M7jWe12510 for ; Thu, 22 Aug 2002 17:15:32 +0930 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by dsto-ms2.dsto.defence.gov.au (Content Technologies SMTPRS 4.2.10) with ESMTP id ; Thu, 22 Aug 2002 17:16:30 +0930 Received: from salex001.dsto.defence.gov.au (salex001.dsto.defence.gov.au [131.185.2.9]) by muttley.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id RAA15329; Thu, 22 Aug 2002 17:11:57 +0930 (CST) Received: from squirm.dsto.defence.gov.au ([131.185.75.211]) by salex001.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id PMGC62MB; Thu, 22 Aug 2002 17:11:57 +0930 Date: Thu, 22 Aug 2002 17:01:03 +0930 (CST) From: "Wilkinson,Alex" X-X-Sender: wilkinsa@squirm.dsto.defence.gov.au Reply-To: Alex.Wilkinson@dsto.defence.gov.au To: Chris Linstruth Cc: Matthew Emmerton , Subject: Re: Open files and Swap Space Errors (fwd) In-Reply-To: Message-ID: <20020822170023.X7929-100000@squirm.dsto.defence.gov.au> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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 ran out of inodes ? - aW Actually, I readily get the errors from systat -a. The system isn't grinding to a halt, it's just reporting swap errors and file table full when pstat -s and sysctl show, plainly, that they're not even close to their maximums. -- Chris Linstruth QNET 1529 East Palmdale Blvd Suite 200 Palmdale, CA 93550 (661) 538-2028 On Wed, 21 Aug 2002, Matthew Emmerton wrote: > > ---------- Forwarded message ---------- > > Date: Wed, 21 Aug 2002 12:26:37 -0700 (PDT) > > From: Chris Linstruth > > To: freebsd-questions@freebsd.org > > Subject: Open files and Swap Space Errors > > > > I have a sendmail server giving me resource allocation errors but > > it looks to me like plenty of file handles and swap space are > > available.... Any thoughts? > > > > FreeBSD x.x.x 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Tue Jun 11 06:14:12 GMT > 2002 murray@builder.freebsdmall.com:/usr/src/sys/compile/GENERIC i386 > > > > # pstat -s > > Device 1K-blocks Used Avail Capacity Type > > /dev/da0s1b 262016 9856 252160 4% Interleaved > > > > # sysctl -a | grep files > > kern.maxfiles: 8080 > > kern.maxfilesperproc: 3636 > > kern.openfiles: 383 > > p1003_1b.mapped_files: 0 > > > > # limits > > Resource limits (current): > > cputime infinity secs > > filesize infinity kb > > datasize 524288 kb > > stacksize 65536 kb > > coredumpsize infinity kb > > memoryuse infinity kb > > memorylocked infinity kb > > maxprocesses 1818 > > openfiles 3636 > > sbsize infinity bytes > > > > Running sysctl -a reports too many of these to post here: > > > > swap_pager_getswapspace: failed > > swap_pager_getswapspace: failed > > swap_pager_getswapspace: failed > > swap_pager_getswapspace: failed > > > > and > > > > <3>file: table is full > > <3>file: table is full > > <3>file: table is full > > <3>file: table is full > > <3>file: table is full > > > > And a few like this: > > <3>pid 29289 (sendmail), uid 0, was killed: out of swap space > > > > Any thoughts appreciated. > > -- > > Chris Linstruth > > Well, somehow you are running out of swap space. Even though 'pstat -a' > shows that you've got tons free, that isn't useful since it (presumably) > wasn't taken at the same time your system was grinding to a halt. > > Off the top of my head, there's two things that could cause sendmail to spin > wildly out of control: > 1) misconfigured majordomo which causes bounces to be sent back to the list > (which bounce, and get sent back to the list, ...) > 2) some sort of mail bombing DoS > > If you're running with a high-enough LogLevel in your sendmail.cf, you > should see sender/recipient data in your sendmail logs, and this may give To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message