From owner-freebsd-stable@FreeBSD.ORG Mon Jun 20 15:16:29 2005 Return-Path: X-Original-To: stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D605F16A41F for ; Mon, 20 Jun 2005 15:16:29 +0000 (GMT) (envelope-from freebsd@as9105.com) Received: from sickle.as9105.com (sickle.as9105.com [212.139.129.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F90043D53 for ; Mon, 20 Jun 2005 15:16:28 +0000 (GMT) (envelope-from freebsd@as9105.com) Received: (qmail 46107 invoked by uid 30010); 20 Jun 2005 15:16:25 -0000 Received: from freebsd@as9105.com by sickle.as9105.com by uid 89 with qmail-scanner-1.22 (clamscan: 0.75.1. spamassassin: 2.64. Clear:RC:1(212.74.112.53):. Processed in 1.389997 secs); 20 Jun 2005 15:16:25 -0000 Received: from unknown (HELO d2) (postmaster@as9105.com@212.74.112.53) by sickle.as9105.com with SMTP; 20 Jun 2005 15:16:24 -0000 From: "Danny Cooper" To: "'Doug Barton'" , "'Gleb Smirnoff'" Date: Mon, 20 Jun 2005 16:16:20 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <42B6DC0B.2010303@FreeBSD.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Thread-Index: AcV1qiGwGrxtKgN0SZSq2f+1ohlPogAACWig X-Qmail-Scanner-Message-ID: <111928058467246101@sickle.as9105.com> Message-Id: <20050620151628.0F90043D53@mx1.FreeBSD.org> Cc: stable@FreeBSD.org Subject: RE: named coredumping 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, 20 Jun 2005 15:16:30 -0000 I am receiving the same problems with FreeBSD 5.4-RELEASE (amd64) bind-9.3.1 DELL PE2850 2 x Intel(R) Xeon(TM) CPU 3.20GHz 4 GB RAM named.log.0:19-Jun-2005 11:46:15.945 *** POKED TIMER *** named.log.0:19-Jun-2005 18:34:17.314 *** POKED TIMER *** named.log.0:20-Jun-2005 02:40:46.193 *** POKED TIMER *** Depending on the load the of the server it can happen every hour. In some case's named starts to Max out one CPU and refused to resolve DNS until named is killed and restarted. Danny Cooper -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Doug Barton Sent: 20 June 2005 16:09 To: Gleb Smirnoff Cc: stable@FreeBSD.org Subject: Re: named coredumping Gleb Smirnoff wrote: > Dear colleagues, > > today I've got problem with named exiting on signal 11. Yes, I've searched > archives and found that POKED TIMER is a problem in our threads. > > Has anyone faced this problem and workarounded it? Or may be even fixed it? > Is there anywhere detailed description of the problem? > > Jun 19 06:00:58 ns named[44534]: *** POKED TIMER *** > Jun 19 06:28:40 ns named[44534]: *** POKED TIMER *** > Jun 19 06:49:54 ns named[44534]: *** POKED TIMER *** > Jun 19 07:18:19 ns named[44534]: *** POKED TIMER *** > Jun 19 07:18:38 ns kernel: pid 44534 (named), uid 53: exited on signal 11 > You haven't stated what version of FreeBSD or named you are using. If you're using FreeBSD old enough so that your named is 9.3.0, then you should upgrade to 5-stable, which will as a by product upgrade named to 9.3.1 which has a lot of the threading issues solved. hth, Doug -- This .signature sanitized for your protection _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"