From owner-freebsd-stable@FreeBSD.ORG Mon Aug 24 21:48:42 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7746106568D for ; Mon, 24 Aug 2009 21:48:42 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 6B9F88FC0A for ; Mon, 24 Aug 2009 21:48:42 +0000 (UTC) Received: (qmail 12122 invoked by uid 399); 24 Aug 2009 21:48:36 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 24 Aug 2009 21:48:36 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4A930AAF.2000103@FreeBSD.org> Date: Mon, 24 Aug 2009 14:48:31 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: besko@msu.edu References: <4A92BFE3.5060801@msu.edu> In-Reply-To: <4A92BFE3.5060801@msu.edu> X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: named stop not stopping X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 21:48:42 -0000 Lisa Besko wrote: > We had an issue with the /etc/rc.d/named script this morning where it > looped/hung in the wait_for_pids subroutine. We run a job to restart > named which calls the /etc/rc.d/named script with a stop command. For > some reason named did not stop properly and the process continued to > list PIDs from the wait_for_pids subroutine forever. Has anyone ever > encountered this before? > > We are running 7.2 stable and bind 9.4.3-P3 on an AMD system. First, please verify that you have the latest version of /etc/rc.d/named installed. Second, this could happen if the call in that script to rndc succeeded, but for some reason rndc was not able to actually kill the binary. In that case there should be something in the logs that indicates what the problem is. hth, Doug -- This .signature sanitized for your protection