Hi all,
After I signed a zone and I noticed there were something wrong in the log:
Jul 4 10:21:34 CST-BJ-104 ods-signerd: *** glibc detected ***
/usr/local/sbin/ods-signerd: double free or corruption (!prev):
0x7f006132f020 ***
I knew the ods-signerd process was down, because I met this kind
Hi Matthijs,
I have a zone with "lab" policy in kasp.xml, and its default Resign period is
"PT10M", but I find the log shows the signing is not continuous,bellow is a
brief of the log:
$ cat /var/log/messages | grep "STATS"
Jul 4 05:13:05 CST-BJ-104 ods-signerd: [STATS] example RR[count=0 time=
Quoting Sander Smeenk (ssme...@freshdot.net):
> Should i run something else to satisfy conditions for the sign call?
For those interrested:
Today i switched from SQLite3 to MySQL. Migration was quite easy, really.
I tried it in a test-vm first, the database layouts are identical and i
was able
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
OpenDNSSEC should have no problems signing large zones. From the logs
you posted, I assume you are using 1.3.X. The signer fails to write
the zone due to an assertion failure. Either the adapter is missing or
the zone data is missing. This should
Hi all,
There is something wrong when I signed a zone named examplex, and I can see the
signed file in /signed dir, but the log shows something wrong and I can't see
the details of the signature result. Does anybody know what's the problem?
Jul 3 15:55:14 CST-BJ-103 ods-signerd: [tools] unable t
