From owner-freebsd-current@FreeBSD.ORG  Mon May 12 13:39:34 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 71B7637B401; Mon, 12 May 2003 13:39:34 -0700 (PDT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A334643FB1; Mon, 12 May 2003 13:39:31 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h4CKdMM7048544;
	Mon, 12 May 2003 13:39:26 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200305122039.h4CKdMM7048544@gw.catspoiler.org>
Date: Mon, 12 May 2003 13:39:22 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: rwatson@FreeBSD.org
In-Reply-To: <Pine.NEB.3.96L.1030512100945.76804F-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: alfred@FreeBSD.org
cc: current@FreeBSD.org
Subject: Re: rpc.lockd spinning; much breakage
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 May 2003 20:39:34 -0000

On 12 May, Robert Watson wrote:

> On the server side, rpc.lockd is unusually busy as a result:
> 
>   PID USERNAME   PRI NICE   SIZE    RES STATE    TIME   WCPU    CPU COMMAND
> 47547 root       121    0  1592K  1224K RUN    448:30 98.68% 98.68% rpc.lockd
> 
> Usually the behavior that upsets the client is to run:
> 
> while (1)
>     periodic daily
>     periodic weekly
>     periodic monthly
> end
> 
> The rpc.lockd process remains extremely busy even after crash2 is rebooted
> and the stream of packets is no longer present.
> 
> I'm not sure how to go about debugging these problems, but the current
> scenario basically means I can't get both the crash boxes through their
> daily events if both the client and server are very busy (i.e., if they
> both run their daily events at the same time).  I'm going to reboot cboss
> and the systems and see if that flushes whatever nasty state hangs around,
> but any advice on the debugging process would be helpful.  Is there a way
> to get rpc.lockd on the server to dump it's state to a file?

Why not attach the process in gdb and step through the code to find the
loop?