BIND dying
Terrence Koeman
root at mediamonks.net
Fri Dec 14 03:50:59 UTC 2001
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Forgot to mention:
I have lots and lots of events from named-xfer, which weren't there
when BIND worked correctly. They are not errors though:
12/14/2001,4:50:40
AM,named-xfer.exe,Information,None,3,N/A,NS1,"print_output: short
answer (94, 348), zone <zone> "
12/14/2001,4:50:39
AM,named-xfer.exe,Information,None,3,N/A,NS1,"print_output: short
answer (94, 364), zone <zone> "
12/14/2001,4:50:38
AM,named-xfer.exe,Information,None,3,N/A,NS1,"print_output: short
answer (94, 348), zone <zone> "
Where <zone> is the same zone as in the warnings.
And this goes on and on, about 1 per 10 seconds.
Also my apologies that I cannot tell you the actual zone name. I'm
slaving this zone for a customer.
- --
Regards,
Terrence Koeman
Technical Director/Administrator
MediaMonks B.V. (www.mediamonks.nl)
Please quote all replies in correspondence.
> -----Original Message-----
> From: Terrence Koeman [mailto:root at mediamonks.net]
> Sent: Friday, December 14, 2001 04:45
> To: Danny Mayer; comp-protocols-dns-bind at moderators.isc.org
> Subject: RE: BIND dying
>
> > -----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.
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.1
iQA/AwUBPBl3I3xo/qu3lMSREQJtYQCdG0+ODHy/m9nubp3t6KLmQRVEYWEAn3Ok
/hMhv+KDfj558UIB67ggoRvu
=YFAQ
-----END PGP SIGNATURE-----
More information about the bind-users
mailing list