From owner-freebsd-questions Wed Dec 25 22: 4:10 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 844F337B401 for ; Wed, 25 Dec 2002 22:04:09 -0800 (PST) Received: from haggis.it.ca (haggis.it.ca [216.126.86.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CE2843EA9 for ; Wed, 25 Dec 2002 22:04:09 -0800 (PST) (envelope-from paul@haggis.it.ca) Received: from haggis.it.ca (paul@localhost [127.0.0.1]) by haggis.it.ca (8.12.6/8.12.6) with ESMTP id gBQ63sCD034528 for ; Thu, 26 Dec 2002 01:03:55 -0500 (EST) (envelope-from paul@haggis.it.ca) Received: (from paul@localhost) by haggis.it.ca (8.12.6/8.12.6/Submit) id gBQ63siH034527 for freebsd-questions@freebsd.org; Thu, 26 Dec 2002 01:03:54 -0500 (EST) (envelope-from paul) Date: Thu, 26 Dec 2002 01:03:54 -0500 From: Paul Chvostek To: freebsd-questions@freebsd.org Subject: portmap running amok Message-ID: <20021226010354.A31170@mail.it.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i 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 Infrequently ... that is, perhaps once every few weeks, my mail server grinds to a halt. The load average climbs into the hundreds, processes start getting killed off, and all because something seems to want to launch as many instances of portmap as it possibly can. And for the life o' me, I can't figure out what. The box is currently running 4.7-STABLE, but it's been doing this off and on since 4.4-RELEASE. The box is not an NFS server, but it becomes a client from time to time, and portmap and nfsiod are launched at startup. There are no NFS devices listed in /etc/fstab, there is no /etc/exports and no other NFS-related daemons are running. If I catch things in time (and have a shell already open), I can usually recover with `killall portmap`. If I'm not around (which is usually the case), the box will either grind to a halt requiring a console reset, or merely spontaneously reboot. I can see no other strange behaviour (or network traffic) going on with this box -- aside from this problem, it behaves perfectly. Does any of this sound familiar? Where do I look for the problem? Tnx. -- Paul Chvostek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message