On Fri, 4 Dec 2009, Steve Foster wrote:
Hi Folks,
just to followup on this, I've caputred a core of named when this happens.
From the looks of it there is a deadlock/very long pause occuring as most
of the threads appear to be parked.
The output of the stacktrace suggests that 3 out
Hi,
recently we've had a number of incidents where named has stopped answering
requests and is spinning the CPU. The only symptom we have been able find
is that there are lots and lots of open sockets. We've been unable to find
anything logged that would suggest that there is an issue.
Has a
2 matches
Mail list logo
