[Opendnssec-user] RE: Build problem withBeta 2 version of OpenDNSSEC
rick.zijlker at sidn.nl
Thu Oct 22 14:41:07 UTC 2009
I've had the exact same problem an hour ago when trying to sign without
starting ods-enforcerd. I only started the ods-signer. So it looks like
running ods-enforcerd does the job.
As I am reading this mailing I see "ods-control start" is starting both
of those, is that correct? Does that mean you won't need to run
"ods-signer start" after running "ods-control start" ?
From: opendnssec-user-bounces at lists.opendnssec.org
[mailto:opendnssec-user-bounces at lists.opendnssec.org] On Behalf Of
Alexd at nominet.org.uk
Sent: donderdag 22 oktober 2009 16:32
To: Sitowitz, Paul
Cc: opendnssec-user-bounces at lists.opendnssec.org; Rickard Bondesson;
opendnssec-user at lists.opendnssec.org
Subject: RE: [Opendnssec-user] RE: Build problem withBeta 2 version of
> 4. used ods-ksmutil to add both zones
> 5. Had to manually create the signer configuration files as the
> software was giving errors that they did not exist (these were
> previously generated automatically at the first time of signing):
> [root]/usr/local/var/opendnssec/signconf: ods-signer
> connecting to /var/run/opendnssec/engine.sock
> cmd> sign example.com
> "Error reading zone config for example.com: [Errno 2] No such file
> or directory: u'/usr/local/var/opendnssec/signconf/example.com.xml'"
I found that killing the ods-enforcerd, running "ods-ksmutil update",
then restarting the ods-enforcerd and ods-signer, and running "update"
in the ods-signer, seems to load the added zone successfully.
There's probably a better way.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Opendnssec-user