From owner-freebsd-questions@FreeBSD.ORG Mon Dec 15 13:47:27 2003 Return-Path: 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 74A1F16A4CE for ; Mon, 15 Dec 2003 13:47:27 -0800 (PST) Received: from optima.cs.arizona.edu (optima.cs.arizona.edu [192.12.69.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7316743D33 for ; Mon, 15 Dec 2003 13:47:26 -0800 (PST) (envelope-from jdavis@cs.arizona.edu) Received: from cs.arizona.edu (bsod.cs.arizona.edu [172.16.1.9]) hBFLlQRh001861 for ; Mon, 15 Dec 2003 14:47:26 -0700 (MST) (envelope-from jdavis@cs.arizona.edu) Message-ID: <3FDE2BBC.1080906@cs.arizona.edu> Date: Mon, 15 Dec 2003 14:46:36 -0700 From: Jim Davis User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ypserv cpu-loop with group.bygid? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2003 21:47:27 -0000 I'm trying to chase down an intermittant problem with ypserv, running on a FreeBSD 4.8 p-14 system, configured as a slave server. Periodically the ypserv process starts burning huge amounts of CPU -- top will show it at 70%-80% of the system, where normally the usage is well under 10%. In those situations interactive response goes down the drain. That slave server is set up so that it binds to itself as a yp client. Running truss on the ypserv process shows it in a tight loop reading the group.bygid map. I've dumped the group.bygid map contents to a file and run chkgrp(8) on it, thinking perhaps there was some bogus data in the source file or other formatting problem -- but chkgrp doesn't find any errors. There are no error messages being logged while ypserv is buzzing; it's just very, very busy. Any ideas on what to check? Normal yp operation seems to be okay; the problem happens rather infrequently, though it's a showstopper when it does happen.