From owner-freebsd-current@FreeBSD.ORG Fri Jan 16 09:39:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41BC416A4CE for ; Fri, 16 Jan 2004 09:39:22 -0800 (PST) Received: from mailserv1.intrex.net (mailserv1.intrex.net [209.42.192.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id A159F43D55 for ; Fri, 16 Jan 2004 09:38:47 -0800 (PST) (envelope-from vangyzen@stat.duke.edu) Received: from localhost (localhost [127.0.0.1]) by mailserv1.intrex.net (Postfix) with ESMTP id A9D23B856; Fri, 16 Jan 2004 12:38:46 -0500 (EST) Received: from amelia.vangyzen.net (trillian.client.intrex.net [209.42.213.136]) by mailserv1.intrex.net (Postfix) with ESMTP id 2FD90B819; Fri, 16 Jan 2004 12:38:46 -0500 (EST) From: Eric van Gyzen Organization: ISDS, Duke University To: Dan Nelson Date: Fri, 16 Jan 2004 12:38:45 -0500 User-Agent: KMail/1.5.4 References: <200401151516.03897.vangyzen@stat.duke.edu> <20040115230708.GB53031@dan.emsphone.com> In-Reply-To: <20040115230708.GB53031@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401161238.45865.vangyzen@stat.duke.edu> X-Virus-Scanned: by viruswatch at intrex.net cc: freebsd-current@freebsd.org Subject: Re: rpc.lockd resource starvation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2004 17:39:22 -0000 Dan Nelson wrote: > In the last episode (Jan 15), Eric van Gyzen said: > > I'm running 5.1-RELEASE on my NFS server and my ~50 NFS clients. > > Over a period of a few weeks, the rpc.lockd daemon on the NFS server > > will consume all the privileged udp ports and start using > > high-numbered ports. With no available privileged udp ports, the > > server is unable to mount NFS shares from other machines. (There are > > probably several other unfortunate consequences of which I am not yet > > aware...) Is this behavior expected from rpc.lockd, or might it be a > > bug (or just me breaking my systems again)? > > wow > > I think you just told me why my two busiest NFS servers had to be > rebooted a few months ago (one with 440 days of uptime :( ). Does the > mount fail with "mount: Can't assign requested address"? Yep. > If so, it > also happens on 4.x servers. Currently, they have 214 and 109 open > reserved ports (after 102 and 73 days uptime, respectively), and I'm > betting there are no more than 5 files actually locked on either > system. I wonder if it's just not closing sockets when it's done with > them? Sounds like a reasonable guess to me. I doubt there are more than 424 locked files on my server (the default number of available low-numbered ports). I could be wrong, though...I wonder how I could determine which files it currently holds locked... Eric -- Eric van Gyzen Sr. Systems Programmer http://www.stat.duke.edu/~vangyzen/ ISDS, Duke University