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? -- \ “Pinky, are you pondering what I'm pondering?” “I think so, | `\ Brain, but this time *you* put the trousers on the chimp.” | _o__) —_Pinky and The Brain_ | Ben Finney <b...@benfinney.id.au>
signature.asc
Description: Digital signature
