bind-8.2.2_p7 chrooted / named-xfer fails (sigpipe)

[Jim Reid]

>>>>> "Ricardo" == Ricardo Manuel Oliveira <rmo at eurotux.com> writes:


    Ricardo> I have a bind-8.2.2P7 running perfectly, chrooted, except
    Ricardo> for the zone-transfers; I get these kind of messages in
    Ricardo> the logs:
    >>
    Ricardo> ns named[30012]: named-xfer "domain.com" exited with signal 13
    >>
    Ricardo> I have verified that, running the named-xfer by hand, it
    Ricardo> works like a charm.
    >>  Are you running the version of named-xfer that comes with the
    >> version of BIND that you're running? If so, can you run
    >> named-xfer by hand successfully from your chroot jail? 

    Ricardo> chroot /chroot/dns bash# named-xfer -z domain.com -f BLA xxx.xxx.xxx.xxx

    Ricardo> I get the BLA file, with the complete zone, as well as a
    Ricardo> ns named[31012]: IP/TCP connection from
    Ricardo> [xxx.xxx.xxx.xxx].1234 (fd 8) in the primary server's
    Ricardo> logs.

    Ricardo>  Any ideas?

I repeat my first question. Is the version of named-xfer that's in the
chroot jail the one that is shipped with the version of named? You
can't use (say) an 8.1 named-xfer with an 8.2.2 named.