named-xfer - premature EOF
klawson at aetinc.com
Thu Mar 8 22:55:15 UTC 2001
Yep. It was memory. I restarted named on the primary and the memory went
from 99% used to 60% used and everything is working fine now. Thanks for
From: Danny Mayer [mailto:mayer at gis.net]
Sent: Wednesday, March 07, 2001 9:57 PM
To: Lawson_Kris; 'bind-users at isc.org'
Subject: Re: named-xfer - premature EOF
Take a look at the master that it's transferring FROM. See if it's
out of memory. If so you need to increase it's page/swap file. You may see
nothing in the logs because the code was not logging this error. This was
fixed in a recent build. The problem is NOT on the slave.
At 05:29 PM 3/7/01, Lawson_Kris wrote:
> We started receiving this message on our secondary at 3:02pm last
>Tuesday. However, up until yesterday the machine was resolving okay. Now
>it only resolves some things. I cannot find the root of this error. If
>anyone knows how to resolve this please let me know.
>[root at ns tmp]# named-xfer -z domain.name -f /usr/tmp/domain -s 0 -d 10
>-l /usr/tmp/debug -t /usr/tmp/trace xxx.xxx.xxx.xxx
>named-xfer: send AXFR query 0 to xxx.xxx.xxx.xxx
>named-xfer: premature EOF, fetching "domain.name"
>That's about all I have to go on. The debug file shows what appears to be
>normal info but ends with this:
>error receiving zone transfer
>Terre Haute, In
More information about the bind-users