On Tue, Jan 5, 2010 at 09:44, Ben Finney <ben+deb...@benfinney.id.au> wrote: > On 22-Dec-2009, Ben Finney wrote: >> The only way I've found to restore service is to ‘sudo killall -KILL >> named’ and restart the server, which of course doesn't give much >> opportunity to find out what's wrong. >> >> I have been trying to narrow down what might be a proximate cause >> for the bug; but so far all I know is that it is more likely to >> occur when there is a lot of network traffic. There are no log >> unusual log messages from the server when the process runs into >> trouble. >> >> What can I do to further diagnose this failure on this machine? > > This continues to happen frequently. > > What diagnosis can be done? Is there some invocation of ‘strace’ or > ‘gdb’ I can use to gather more information about the failure?
Ben, have you tried writing to bind-users? Your question would probably hit much wider audience. Discussing it directly in Debian BTS would only make sense if this behaviour doesn't happen in vanilla upstream bind. Ondrej -- Ondřej Surý <ond...@sury.org> http://blog.rfc1925.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
