Re: rndc stop hangs, named stuck at FUTEX WAIT

named reference counts objects. When there is a unbalanced attach/detach, missing dns_rdataset_disassociate somewhere in the code one can get this on shutdown as named frees all memory. The only outstanding one I'm aware of is this one which will be fixed in the next maintanence release. https:/

RE: still have named memory leak

Here’s some suggestions from ISC on capturing information on this memory growth issue: https://kb.isc.org/article/AA-01208 Frank From: bind-users-boun...@lists.isc.org [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Kevin Oberman Sent: Saturday, December 13, 2014 12:07 PM To: Muku

Re: still have named memory leak

On Fri, Dec 12, 2014 at 8:12 AM, Mukund Sivaraman wrote: > Hi Len > > On Fri, Dec 12, 2014 at 09:52:23AM -0600, lcon...@go2france.com wrote: > > binary upgraded Freebsd 10 to Freebsd 10.1 > > > > named 9.10.1, compiled from source > > > > at named start, 305 MB memory > > > > after several hours

Re: rndc stop hangs, named stuck at FUTEX WAIT

On Sat, Dec 13, 2014 at 11:05:52AM -0500, Chuck Anderson wrote: > For the second time (at least), an automatic BIND update on Scientific > Linux 6 (RHEL 6 clone) failed to restart the named process. The RPM > package runs this to restart: ... > Now I believe what is happening is "rndc stop" is han

rndc stop hangs, named stuck at FUTEX WAIT

For the second time (at least), an automatic BIND update on Scientific Linux 6 (RHEL 6 clone) failed to restart the named process. The RPM package runs this to restart: postuninstall scriptlet (using /bin/sh): /sbin/ldconfig if [ "$1" -ge 1 ]; then /sbin/service named try-restart >/dev/null 2>&