From owner-freebsd-current@FreeBSD.ORG Tue Apr 8 16:39:37 2003 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 8A70C37B401 for ; Tue, 8 Apr 2003 16:39:37 -0700 (PDT) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10DF143FB1 for ; Tue, 8 Apr 2003 16:39:37 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0311.cvx21-bradley.dialup.earthlink.net ([209.179.193.56] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 1932gc-0004Ai-00; Tue, 08 Apr 2003 16:39:31 -0700 Message-ID: <3E935D63.DAC8BBF8@mindspring.com> Date: Tue, 08 Apr 2003 16:38:11 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dan Nelson References: <3E92E509.A7A43986@mindspring.com> <20030408174218.GE86482@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4e549bb968fd7435524932749f34295be387f7b89c61deb1d350badd9bab72f9c350badd9bab72f9c cc: Dan Pelleg cc: current@freebsd.org Subject: Re: NIS exhausts system resources 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: Tue, 08 Apr 2003 23:39:37 -0000 Dan Nelson wrote: > In the last episode (Apr 08), Terry Lambert said: > > Dan Pelleg wrote: > > > When does this happen, you ask? I triggered it this morning by > > > booting the machine when the NIS server was down. I had also seen > > > it in the past when configuring NIS, and it happened as soon as I > > > set the domainname. Any ideas? I can provide packet captures on > > > request, however note the failure where the server is down. > > > > Historical behaviour when the NIS server is down has been for the > > client machines to hang until the NIS server is back up. > > I've never seen that here. I used to run a SPARC SunOS 4.1.3_U1 client machine off an SunOS 4.1.3_U2 NIS server as my primary engineering workstation. Trust me, the FreeBSD code is different. > I have three NIS servers though, so there > has never been a case when all NIS resources were unavailable. Usually > what I see in the logs are: > > Mar 12 13:52:13 ypbind[113]: NIS server [10.0.0.11] for domain not responding > Mar 12 13:52:13 ypbind[113]: NIS server [10.0.0.89] for domain OK > > Was it ypbind that was hogging all the file descriptors, or what, I > wonder? No. Likely, it was something that held an unrelated descriptor open over a call to the NIS as a result of some map lookup, rather than closing the unrelated descriptor before making the map request. The big hint here is that it was complaining about /etc/hosts.access while a broken NIS request was still outstanding. -- Terry