BIND dying

[Terrence Koeman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
> Behalf Of Danny Mayer
> Sent: Friday, December 14, 2001 03:21
> To: root at mediamonks.net; comp-protocols-dns-bind at moderators.isc.org
> Subject: Re: BIND dying
>
> At 09:35 AM 12/12/01, Terrence Koeman wrote:
> >
> >Hello,
> >
> >I suddenly have BIND dying on me because of a failed zone transfer.
> >
> >This is in my logfile:
> >
> >12-Dec-2001 09:32:34.000 default: warning: zone transfer timeout for
> >"zone"; pid 536 kill failed Errcode: 10035: Operation would block
> >12-Dec-2001 09:33:04.000 default: warning: zone transfer timeout for
> >"zone"; second kill pid 536 - forgetting, processes may accumulate
> >
> >BIND 8.2.5-NT on Windows 2000 AS SP2
> 
> It's most unlikely that warning caused BIND to die. These 
> messages indicate
> that you have a timeout during the attempted zone transfer. You 
> should check
> your network for connectivity to the other server.  

The connectivity is not perfect, but it's good enough.

> Is this the slave? 

Yes.

> What other messages are there in the logs to indicate that it died? 

None, they are always the last messages in the log before BIND dies and
is automatically restarted by the service manager. The service manager
logs an unexpected termination to the eventlog.

Event ID: 7031

"The ISC BIND service terminated unexpectedly.  It has done this 56
time(s).  The following corrective action will be taken in 1000
milliseconds: Restart the service."

> How large is the zone file?

About 32Mb.

I wrote a script to save the PID files in a different directory each
startup, and I'm not sure but it seems the pid BIND is trying to kill
('pid xxx kill') is not a pid of named-xfer but of named itself, and
thus BIND is killing itself while it should kill a named-xfer process.

- -- 
Regards,

Terrence Koeman

Technical Director/Administrator
MediaMonks B.V. (www.mediamonks.nl)

Please quote all replies in correspondence. 

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.1

iQA/AwUBPBl1qHxo/qu3lMSREQKZKACgkkmL//E2Guoz99f0Tt75MLn8IMoAoJpq
UajF/s3ER+MvNDRUjxYN2vpp
=XbrM
-----END PGP SIGNATURE-----