On Wednesday, 25 December 2002 21:54, Richard wrote: > On Wed, 25 Dec 2002, J.Reilink wrote: > > I've had exactly the same on our corperate primary nameserver (Slackware > > with bind 9.2.1), because there was no logging I couldn't find out why > > bind stopped working. > > Take a look at memory usage when Bind stop's working and monitor for some > time how much memory Bind is using. If that amount is growing, Bind > probably got a memory leak. ( isn't the first time :( )
I've made the mistake of running bind with debugging (to find one bug), and have bind create a 2GB /var/named/named.run file. Bind crashed because that file was too big. Doh! If your Bind crashes regularly after X days, see if its creating its own (non-syslog) log file. Effects are similar to a memory leak. > Greetings, > > Richard. > > ---- > Paul Vixie in an interview with Sendmail.net: > > Now that the Internet has the full spectrum of humanity as users, > the technology is showing its weakness: it was designed to be > used by friendly, smart people. Spammers, as an example of a class, > are neither friendly nor smart. -- Berend De Schouwer