From owner-freebsd-bugs Tue Sep 10 12:39:22 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E91837B400 for ; Tue, 10 Sep 2002 12:39:14 -0700 (PDT) Received: from south.nanolink.com (south.nanolink.com [217.75.134.10]) by mx1.FreeBSD.org (Postfix) with SMTP id E9D3B43E75 for ; Tue, 10 Sep 2002 12:39:12 -0700 (PDT) (envelope-from roam@straylight.ringlet.net) Received: (qmail 68612 invoked by uid 85); 10 Sep 2002 19:48:22 -0000 Received: from discworld.nanolink.com (HELO straylight.ringlet.net) (217.75.135.248) by south.nanolink.com with SMTP; 10 Sep 2002 19:48:21 -0000 Received: (qmail 6586 invoked by uid 1000); 10 Sep 2002 19:38:01 -0000 Date: Tue, 10 Sep 2002 22:38:01 +0300 From: Peter Pentchev To: Ross Finlayson Cc: freebsd-bugs@freebsd.org Subject: Re: named crash (again) Message-ID: <20020910193801.GB4158@straylight.oblivion.bg> Mail-Followup-To: Ross Finlayson , freebsd-bugs@freebsd.org References: <4.3.1.1.20020910003032.00bf4860@laptop-localhost> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cNdxnHkX5QqsyA0e" Content-Disposition: inline In-Reply-To: <4.3.1.1.20020910003032.00bf4860@laptop-localhost> User-Agent: Mutt/1.5.1i X-Virus-Scanned: by Nik's Monitoring Daemon (AMaViS perl-11d ) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 10, 2002 at 12:32:04AM -0700, Ross Finlayson wrote: > A few days ago, I reported a "named" crash. Tonight, I saw it again: [snip crash info] > Strangely, the error occurred almost exactly 6 days after the previous=20 > occurrence. This means that you may have indeed stumbled upon a genuine BIND bug. Six days is the default time-to-live on a zone NS record; this probably means that BIND crashed last time while either processing the record or building a reply packet for a client, and now, six days later, when the record expired, the resolver tried to look it up again, and crashed in the same way. Could you try to correlate the time of the crash with something either you or your users were doing? Or is that too much to ask? :) Do you have the ability (disk space, CPU utilization) to turn on BIND's query log and (possibly another six days from now) examine the queries issued around the time of the crash? G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 If you think this sentence is confusing, then change one pig. --cNdxnHkX5QqsyA0e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9fkoZ7Ri2jRYZRVMRAjyLAKCiB4xOXH/7bQ3PgO/RhxVEa20PkACeJFU/ NaafzocTDCgzLKGRSMVhWR0= =yJR0 -----END PGP SIGNATURE----- --cNdxnHkX5QqsyA0e-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message