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 with the ‘bind9’ package version 1:9.6.1.dfsg.P2-1. I have downgraded to Lenny's current ‘bind9’, version 1:9.5.1.dfsg.P3-1+lenny1, and the problem has not recurred for the past 24 hours. At this point I am confident the bug is in Squeeze's version and not in Lenny's version. What diagnosis can be done? -- \ “Apologize, v. To lay the foundation for a future offense.” | `\ —Ambrose Bierce, _The Devil's Dictionary_, 1906 | _o__) | Ben Finney <b...@benfinney.id.au> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
