From owner-freebsd-stable@FreeBSD.ORG Tue Aug 25 14:38:14 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 7B864106568C for ; Tue, 25 Aug 2009 14:38:14 +0000 (UTC) (envelope-from besko@msu.edu) Received: from sys08.mail.msu.edu (sys08.mail.msu.edu [35.9.75.108]) by mx1.freebsd.org (Postfix) with ESMTP id 3E31A8FC19 for ; Tue, 25 Aug 2009 14:38:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=msu.edu; s=mail; h=Message-ID:Date:From:Reply-To:MIME-Version:To:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; bh=fOciKL0Z0hEJbMkWXbjKC5HA/7sYl21yZWK65MJCaDA=; b=AOCJZHBZ92Drp ae849K0bkGz6CTIkoy4oZS461PHjxDoONdUjkP3gsTJt9o5mZ8RpsEYm0B/1uOK+ yeBdMz86GuBvMJi2DXAkr78MudVvvt9acP55sEYupK/smr8pux1vGeTpWxDqcVwq 4EL8LyuSI6vB2zviCGh151F2hQRNRU= Received: from user-718268.user.msu.edu ([35.10.4.118]) by sys08.mail.msu.edu with esmtpsa (Exim 4.69 #1) (TLSv1:AES256-SHA:256) id 1MfxA4-0000l7-N6 for freebsd-stable@freebsd.org; Tue, 25 Aug 2009 10:38:12 -0400 Message-ID: <4A93F756.8010900@msu.edu> Date: Tue, 25 Aug 2009 10:38:14 -0400 From: Lisa Besko User-Agent: Thunderbird 2.0.0.16 (X11/20080918) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4A92BFE3.5060801@msu.edu> <4A930AAF.2000103@FreeBSD.org> In-Reply-To: <4A930AAF.2000103@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus: None found by Clam AV Subject: Re: named stop not stopping X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: besko@msu.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 14:38:14 -0000 Doug Barton wrote: > 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. > I'm running a current supported version of bind. It's the one that was included with 7.2 stable and has been patched. The only thing I see in my logs is the icmp unreach message but that does not start until after the named stop command was issued. kernel: Limiting icmp unreach response from 259 to 200 packets/sec Currently we changed the way we run our restart script to do a kill -9 if all else fails. The /etc/rc.d/named script uses a kill -TERM if the original rcnd stop fails. In this case that wasn't enough. Thanks for the input. -- Lisa Besko