From owner-freebsd-rc@FreeBSD.ORG Thu Jul 19 16:12:53 2007 Return-Path: X-Original-To: freebsd-rc@FreeBSD.org Delivered-To: freebsd-rc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 97D7916A401; Thu, 19 Jul 2007 16:12:53 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (thingy.kcilink.com [74.92.149.59]) by mx1.freebsd.org (Postfix) with ESMTP id 6C4E913C4A6; Thu, 19 Jul 2007 16:12:53 +0000 (UTC) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id B95DEB80A; Thu, 19 Jul 2007 11:57:41 -0400 (EDT) In-Reply-To: <200707190936.l6J9a0m0043622@freefall.freebsd.org> References: <200707190936.l6J9a0m0043622@freefall.freebsd.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <26F03516-97A0-4585-B14D-341BA25E50CB@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 19 Jul 2007 11:57:40 -0400 To: dougb@FreeBSD.org X-Mailer: Apple Mail (2.752.2) Cc: freebsd-rc@FreeBSD.org Subject: Re: conf/103976: rc.d/named restart failure X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jul 2007 16:12:53 -0000 On Jul 19, 2007, at 9:36 AM, dougb@FreeBSD.org wrote: > Are you saying that with the output that you pasted there > IS still a named running, and then the 'start' fails for > that reason? Yes, that seems to be the case. verified just now. named is running. I try to restart. it takes 3 attempts before it succeeds. it seems on the second attempt it might have actually killed named, but did not restart it because the named process took too long to actually exit between the time it was asked to exit and the time the new process was launched. [root@bluefish]# ps axuw | grep ^bind bind 54478 8.6 8.2 174428 170848 ?? Rs 5Mar07 4346:06.96 / usr/sbin/named -t /var/named -u bind [root@bluefish]# /etc/rc.d/named restart Stopping named. named already running? (pid=54478). [root@bluefish]# /etc/rc.d/named restart Stopping named: rndc failed, trying killall: . named already running? (pid=54478). [root@bluefish]# /etc/rc.d/named restart Stopping named: rndc failed, trying killall: No matching processes were found Starting named. [root@bluefish]# ps axuw | grep ^bind bind 31155 7.9 0.3 9484 6376 ?? Rs 11:51AM 0:00.42 /usr/ sbin/named -t /var/named -u bind [root@bluefish]# uname -a FreeBSD bluefish.kcilink.com 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #3: Tue Oct 3 10:49:29 EDT 2006 vivek@redfish.kcilink.com:/n/ lorax1/usr6/obj.amd64/n/lorax1/usr6/src/sys/KCI64SMP amd64 I tried it one more time just to be sure: [root@bluefish]# ps axuw | grep ^bind bind 31155 11.0 0.6 14732 11640 ?? Rs 11:51AM 0:19.93 /usr/ sbin/named -t /var/named -u bind [root@bluefish]# /etc/rc.d/named restart Stopping named. named already running? (pid=31155). [root@bluefish]# ps axuw | grep ^bind [root@bluefish]# /etc/rc.d/named restart Stopping named: rndc failed, trying killall: No matching processes were found Starting named. [root@bluefish]# So it does seem that there needs to be something that waits for named to finish exiting before starting it again. This is a pretty fast box: CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.12-MHz K8-class CPU) dual core with 2GB RAM and pretty much all it does is DNS and logfile collecting.