Re: named coredumping
On Thu, Jun 30, 2005 at 12:57:32PM -0500, Doug Barton wrote: D> FYI, I had a chat with the ISC folks this week, and they said in clear terms D> that enabling threads on current versions of BIND would be a pessimization. D> I have already turned off threads in the port of 9.3.1, and am looking at D> doing that for the base as well. D> D> Could you give the port a try for now (with or without the option to D> overwrite the base system BIND), and let me know if that helps/solves your D> problems? I'll rebuild base bind with threads disabled, and report after a week. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named coredumping
FYI, I had a chat with the ISC folks this week, and they said in clear terms that enabling threads on current versions of BIND would be a pessimization. I have already turned off threads in the port of 9.3.1, and am looking at doing that for the base as well. Could you give the port a try for now (with or without the option to overwrite the base system BIND), and let me know if that helps/solves your problems? 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 "[EMAIL PROTECTED]"
Re: named coredumping
On Tue, Jun 21, 2005 at 10:17:04AM -0700, Doug Barton wrote: D> > D> Thanks for clarifying guys. Are either of you in a position to upgrade to D> > D> -stable and see if the problem persists? D> > D> > Does STABLE have an other version of BIND? D> D> Not newer than 5.4, no, but it does have other things fixed. Which ones? I can patch my system and test. I probably won't upgrade whole system. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named coredumping
Gleb Smirnoff wrote: > On Mon, Jun 20, 2005 at 11:02:57AM +0200, Doug Barton wrote: > D> Thanks for clarifying guys. Are either of you in a position to upgrade to > D> -stable and see if the problem persists? > > Does STABLE have an other version of BIND? > Not newer than 5.4, no, but it does have other things fixed. 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 "[EMAIL PROTECTED]"
Re: named coredumping
On Mon, Jun 20, 2005 at 11:02:57AM +0200, Doug Barton wrote: D> Thanks for clarifying guys. Are either of you in a position to upgrade to D> -stable and see if the problem persists? Does STABLE have an other version of BIND? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named coredumping
On 21/06/2005, at 1:16 AM, Danny Cooper wrote: 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. I've seen the exact same thing on my dual AMD64 caching name server, I can only think it is something to do with the Dual CPU's, bind 9.3.1 and FreeBSD 5.4, even an upgrade to stable as of a week ago hasn't fixed it, so for now I have a wrapper script that looks for 99+ % cpu usage and then kill -9 and /etc/rc.d/named start . I'd love to get to the bottom of it, but know one has come across this before it seems. Have a look at my posts on heavy named problems in late may. Cheers, Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named coredumping
Thanks for clarifying guys. Are either of you in a position to upgrade to -stable and see if the problem persists? 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 "[EMAIL PROTECTED]"
Re: named coredumping
On Mon, Jun 20, 2005 at 08:08:59AM -0700, Doug Barton wrote: D> Gleb Smirnoff wrote: D> > Dear colleagues, D> > D> >today I've got problem with named exiting on signal 11. Yes, I've searched D> >archives and found that POKED TIMER is a problem in our threads. D> > D> >Has anyone faced this problem and workarounded it? Or may be even fixed it? D> >Is there anywhere detailed description of the problem? D> > D> >Jun 19 06:00:58 ns named[44534]: *** POKED TIMER *** D> >Jun 19 06:28:40 ns named[44534]: *** POKED TIMER *** D> >Jun 19 06:49:54 ns named[44534]: *** POKED TIMER *** D> >Jun 19 07:18:19 ns named[44534]: *** POKED TIMER *** D> >Jun 19 07:18:38 ns kernel: pid 44534 (named), uid 53: exited D> >on signal 11 D> > D> D> You haven't stated what version of FreeBSD or named you are using. If D> you're using FreeBSD old enough so that your named is 9.3.0, then you D> should upgrade to 5-stable, which will as a by product upgrade named to D> 9.3.1 which has a lot of the threading issues solved. That is 5.4-RELEASE, BIND 9.3.1 -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: named coredumping
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doug Barton Sent: 20 June 2005 16:09 To: Gleb Smirnoff Cc: [EMAIL PROTECTED] 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 "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 "[EMAIL PROTECTED]"
named coredumping
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 -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
