[Opendnssec-user] Re: zone-fetcher not renaming zones after AXFR

[James Dempsey]

On Fri, Oct 22, 2010 at 10:32 AM, James Dempsey <jamespd at gmail.com> wrote:

> Hi all,
>
> I'm having a problem with the zone fetcher while running the OpenDNSSEC
> trunk (r4129) on Debian Squeeze.  Zones appear to be fetched and the
> resulting /var/opendnssec/unsigned/<zone-name>.axfr file looks complete, but
> OpenDNSSEC doesn't rename the file to /var/opendnssec/unsigned/<zone-name>
> and sign it.  Has anyone else seen this, or can anyone point me to the line
> of code that renames the .axfr files?
>
> I see the zone fetch success in syslog:
>
> ods-signerd: zone fetcher received NOTIFY for zone <zone-name>
> ods-signerd: zone fetcher transferred zone <zone-name> serial 2010102164
> successfully
>
> On the console, I get the following messages:
>
> /bin/cp: cannot stat `/var/opendnssec/unsigned/<zone-name>': No such file
> or directory
> Zone <zone-name> scheduled for immediate re-sign.
>
>
> Cheers,
> James
>

As best I can tell, this rename was done in version 1.1.3
in OpenDNSSEC-1.1.3/signer/signer_engine/Zone.py:279.  I can't find the
equivalent code in trunk.  I attempted a quick fix by changing "%s.axfr" to
"%s" in signer/src/tools/zone_fetcher.c:971

    snprintf(dest_file, sizeof(dest_file), "%s.axfr",

While this seemed to remove the roadblock, I'm still seeing an initial round
of errors on the console before OpenDNSSEC starts processing data.

/bin/cp: cannot stat `/var/opendnssec/unsigned/<zone-name>': No such file or
directory

Thanks,
James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendnssec.org/pipermail/opendnssec-user/attachments/20101022/c0e664b9/attachment.htm>