Query timeouts on FreeBSD 7 over network

Vinny Abello vinny at tellurian.com
Sun Aug 10 05:21:02 UTC 2008

> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> Behalf Of Thomas Rasmussen
> Sent: Friday, August 08, 2008 4:27 PM
> To: bind-users at isc.org
> Subject: Re: Query timeouts on FreeBSD 7 over network
> Vinny Abello wrote:
> > The only way I've gotten it to work on FreeBSD 7 in a stable manner
> is without threads. What were you referring to that didn't work
> perfectly?
> > -Vinny
> >
> >
> >
> Hello there,
> I have bind9.4.2-P2 running on two recursive servers at around 1000
> queries / second on FreeBSD 7 stable from a couple of weeks ago. This
> is
> with the default "make config" settings, which on all my machines means
> threads enabled, although FreshPorts disagree on the default setting
> for
> threads: http://www.freshports.org/dns/bind94/
> I compiled the port with a larger (65000) FD_SETSIZE and increased
> kern.maxfiles (also to 65000) with sysctl but other than that the
> machines are perfectly standard. I am not even sure larger FD_SETSIZE
> and increasing kern.maxfiles is neccesary with -P2 but it helped a bit
> with all the issues I was having with -P1. At least -P2 doesn't use
> nearly as many file descriptors and sockets as -P1, so I guess it might
> not be neccesary anymore. I don't know what the problem is supposed to
> be with threads on FreeBSD7 but I haven't run into it, it is very
> stable
> and has been for a few weeks now.

I've found the issues are specific to BIND 9.5.0 releases and FreeBSD 7.0 with threads enabled. I downgraded to BIND 9.4.2-P2 with threads enabled and have no problems with memory growing at an insane rate anymore and BIND eventually crashing due to exhaustion of memory. I'm going to try and get a traceback from a core dump on a new test machine as I'm happily running 9.4.2-P2 on FreeBSD 7.0 with threads enabled and it's working great.


More information about the bind-users mailing list