named-xfer error

[Jonathan Fanti]

The logs looks something like this:

ns1# tail -f /var/log/messages
Jan 10 09:29:16 ns1 named[109]: named-xfer "alimango.co.uk" exited with 
signal 6
Jan 10 09:29:18 ns1 named[109]: named-xfer "hazlewoodmotorsport.co.uk" 
exited with signal 6

Blah, blah, blah.... goes on like this all domains.

when I transfer the domains manually:
./named-xfer -z alimango.co.uk -f ../etc/namedb/slave/alimango.co.uk 
212.67.193.75

This works fine, and the domain is transfered.

Cheers,

Jon.

Kevin Darcy wrote:

> Signal 6 is an IOT or ABRT signal. This could be anything. Is named-xfer
> logging anything to syslog when this happens? What happens if you try to
> run named-xfer manually in the sandbox?
> 
> 
> - Kevin
> 
> Jonathan Fanti wrote:
> 
> 
>> Hi,
>> 
>> Im trying to run bind 8.2.2-P7 on freeBSD 4.2 as a sandbox proccess, all
>> seems well, except that when I try to do domain transfers between
>> servers, named-xfer exits with signal 6. What is does this mean? I can't
>> seem to find any reference on named-xfer signal codes.
>> 
>> Thanks,
>> 
>> Jon.
>> 
>> --
>> ICMP - The protocol that likes to go: PING!


-- 
ICMP - The protocol that likes to go: PING!