From owner-freebsd-amd64@FreeBSD.ORG Wed May 25 09:47:45 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FD3016A41C for ; Wed, 25 May 2005 09:47:45 +0000 (GMT) (envelope-from marsgmiro@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2934F43D1F for ; Wed, 25 May 2005 09:47:45 +0000 (GMT) (envelope-from marsgmiro@gmail.com) Received: by zproxy.gmail.com with SMTP id 12so136436nzp for ; Wed, 25 May 2005 02:47:44 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=kvFgum1lvkNHBnm0weBKIgnczzuEVHNQJVbhhEaQA4EV0O/9ekwnO1HwxgOHWEdS6YOcFB19Acr2VGmiSUOuBzIMtIs0FDUjecp+oFRnKxtMsUXY1oIDpJ/0+DsZFi6oECXTGU5oxKBZo+ULdn73gmvK/d7LYFj/y/LurG4fYPY= Received: by 10.36.2.16 with SMTP id 16mr63049nzb; Wed, 25 May 2005 02:47:44 -0700 (PDT) Received: by 10.36.72.13 with HTTP; Wed, 25 May 2005 02:47:44 -0700 (PDT) Message-ID: <28edec3c0505250247428b6db2@mail.gmail.com> Date: Wed, 25 May 2005 17:47:44 +0800 From: "Mars G. Miro" To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: bind 9.3.1 thread issues on FreeBSD 5.3R/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Mars G. Miro" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2005 09:47:45 -0000 Yo list! I think I'm seeing a problem about bind9.3.1 on FreeBSD 5.3R/AMD64. This is addressed by setting WITHOUT_BIND9_THREADS=3Dtrue when compiling the port. This also doesn't happen on FreeBSD 5.4R/AMD64. The problem manifests when shutting down the named daemon where it just would not die gracefully (you have to kill -9 it). Here are the necessary steps to reproduce it: 1) install FreeBSD5.3R/AMD64 2) install bind9.3.1 from ports (set WITH_PORT_REPLACES_BASE_BIND9) 3) configure a simple resolver (# cd /var/named/etc/namedb && sh make-localhost) 4) start named server ( # /etc/rc.d/named start or # named -u bind -t /var/named ) 5) test some dns queries ( dig, nslookup etc) 6) kill named server ( # /etc/rc.d/named stop or # killall named ),=20 [ this is where it happens ... ] if logging is configured, you'd see something like: 5-May-2005 08:44:32.348 database: debug 1: done free_rbtdb(0.0.127.IN-ADDR.= ARPA) 25-May-2005 08:44:32.348 general: debug 3: zone_shutdown: zone authors.bind/CH: shutting down 25-May-2005 08:44:32.348 general: debug 3: zone_shutdown: zone version.bind/CH: shutting down 25-May-2005 08:44:32.349 client: debug 3: client @0x739400: shutdown 25-May-2005 08:44:32.349 client: debug 3: client @0x739400: free 25-May-2005 08:44:32.349 client: debug 3: client @0x739c00: shutdown 25-May-2005 08:44:32.349 client: debug 3: client @0x739c00: accept failed: operation canceled 25-May-2005 08:44:32.349 client: debug 3: client @0x739c00: free 25-May-2005 08:44:32.349 general: debug 3: clientmgr @0x6feb80: clientmgr_destroy 25-May-2005 08:44:32.349 resolver: debug 3: res 0x73ae00: detach 25-May-2005 08:44:32.349 resolver: debug 3: res 0x73ae00: destroy 25-May-2005 08:44:32.349 general: debug 3: dns_requestmgr_detach: 0x7e1000: eref 0 iref 0 25-May-2005 08:44:32.349 general: debug 3: mgr_destroy 25-May-2005 08:44:32.349 database: debug 1: calling free_rbtdb(.) 25-May-2005 08:44:32.349 database: debug 1: done free_rbtdb(.) 25-May-2005 08:44:32.349 database: debug 1: calling free_rbtdb(.) 25-May-2005 08:44:32.349 database: debug 1: done free_rbtdb(.) 25-May-2005 08:44:32.351 resolver: debug 3: res 0x7e1500: detach 25-May-2005 08:44:32.351 resolver: debug 3: res 0x7e1500: destroy 25-May-2005 08:44:32.351 general: debug 3: dns_requestmgr_detach: 0x7f4700: eref 0 iref 0 25-May-2005 08:44:32.351 general: debug 3: mgr_destroy 25-May-2005 08:44:32.351 database: debug 1: calling free_rbtdb(.) 25-May-2005 08:44:32.351 database: debug 1: done free_rbtdb(.) but then the process is still there: root 31645 0.0 0.1 3580 844 ?? SsJ 4:45AM 0:00.02 /usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -ss bind 39312 0.0 0.5 9752 5432 ?? IsJ 8:44AM 0:00.02 /usr/sbin/named -u bind -t /var/named The only way to kill it is kill -9 the pid. Somebody also had some similar issues like this (slapd): http://www.monkey.org/freebsd/archive/freebsd-amd64/200404/msg00076.html w/c is FreeBSD 5.2.X on AMD64. And, as I've said, this doesn't manifest on FreeBSD5.4R/AMD64 nor 5.3/5.4 i386 and the work-around is to compile the port WITHOUT_BIND9_THREADS=3Dtrue, So is anyone else also experiencing this problem? Thanks. cheers mars