named coredumping

[Danny Cooper]

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 at freebsd.org
[mailto:owner-freebsd-stable at freebsd.org] On Behalf Of Doug Barton
Sent: 20 June 2005 16:09
To: Gleb Smirnoff
Cc: stable at 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 <daemon.warn> ns named[44534]: *** POKED TIMER ***
> Jun 19 06:28:40 <daemon.warn> ns named[44534]: *** POKED TIMER ***
> Jun 19 06:49:54 <daemon.warn> ns named[44534]: *** POKED TIMER ***
> Jun 19 07:18:19 <daemon.warn> ns named[44534]: *** POKED TIMER ***
> Jun 19 07:18:38 <kern.info> 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 at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"