[Opendnssec-user] Problems adding largish # of zones

[Havard Eidnes]

> So far the newly started pair of processes seem to be a lot
> better behaved.

It appears I spoke too soon.  Today I awoke to data not flowing
through OpenDNSSEC, and on inspection, it had stopped responding
to notify messages.  Even if i upped the logging level to 10
there was no "action" related to the notify messages in the log.

Furthermore, it also stopped acting on "sign <zone>" commands, it
simply logged

Dec 23 12:59:23 signhost ods-signerd: [cmdhandler] received command sign <zone>[15]
Dec 23 12:59:23 signhost ods-signerd: [cmdhandler] sign zone command
Dec 23 12:59:23 signhost ods-signerd: [zone] reschedule task for zone <zone>
Dec 23 12:59:23 signhost ods-signerd: [scheduler] unschedule task [sign] for zone <zone>
Dec 23 12:59:23 signhost ods-signerd: [scheduler] schedule task [read] for zone <zone>
Dec 23 12:59:23 signhost ods-signerd: [cmdhandler] zone <zone> scheduled for immediate re-sign
Dec 23 12:59:23 signhost ods-signerd: [engine] wake up workers
Dec 23 12:59:23 signhost ods-signerd: [worker[1]] wake up
Dec 23 12:59:23 signhost ods-signerd: [worker[2]] wake up
Dec 23 12:59:23 signhost ods-signerd: [worker[1]] report for duty
Dec 23 12:59:23 signhost ods-signerd: [scheduler] pop task for zone <zone>
Dec 23 12:59:23 signhost ods-signerd: [scheduler] unschedule task [read] for zone <zone>
Dec 23 12:59:23 signhost ods-signerd: [worker[1]] start working on zone <zone>
Dec 23 12:59:23 signhost ods-signerd: [worker[1]] perform task [read] for zone <zone> at 1450871963
Dec 23 12:59:23 signhost ods-signerd: [worker[1]] read zone <zone>
Dec 23 12:59:23 signhost ods-signerd: [cmdhandler] done handling command sign <zone>[15]
Dec 23 12:59:23 signhost ods-signerd: [worker[2]] report for duty
Dec 23 12:59:23 signhost ods-signerd: [worker[2]] nothing to do
Dec 23 12:59:23 signhost ods-signerd: [hsm] libhsm connection ok
Dec 23 12:59:23 signhost ods-signerd: [adapter] read zone <zone> from dns input adapter /usr/pkg/etc/opendnssec/addns.xml
Dec 23 13:00:39 signhost ods-signerd: [cmdhandler] 1 clients in progress...
Dec 23 13:00:39 signhost ods-signerd: [cmdhandler] accept client 21
Dec 23 13:00:39 signhost ods-signerd: [cmdhandler] received command verbosity 10[12]
Dec 23 13:00:39 signhost ods-signerd: [cmdhandler] verbosity command
Dec 23 13:00:39 signhost ods-signerd: [log] switching log to syslog verbosity 10 (log level 12)
Dec 23 13:00:39 signhost ods-signerd: [cmdhandler] done handling command verbosity 10[12]
Dec 23 13:24:15 signhost ods-enforcerd: Received SIGTERM, exiting...

So it noticed I asked it please to re-sign the zone, but it
didn't actually obey.  It also indicated it would run the
addns.xml input adapter, but no sign of it actually doing that
either.  The last line is me losing patience and trying a
restart, which temporarily seems to have restored things into
working order.

This is becoming extremely frustrating...  I realize it's
entering the "quiet period", and it should do so for myself as
well, but here I am and can't really let go of it either.

Regards,

- Håvard
_______________________________________________
Opendnssec-user mailing list
Opendnssec-user at lists.opendnssec.org
https://lists.opendnssec.org/mailman/listinfo/opendnssec-user