<div dir="ltr">Hi,<br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 5, 2013 at 2:13 PM, Volker Janzen <span dir="ltr"><<a href="mailto:voja@voja.de" target="_blank">voja@voja.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Can anyone tell what else should be monitored of the OpenDNSSEC system?<br>
E.g. running processes, PID-files or logfile content?</blockquote><div> <br></div><div>You can monitor the ods-enforcerd and ods-signerd processes, use the "ods-signer running" and there should be a pid file somewhere (depend on the OS or if you compiled yourself). You can also monitor the syslog for the STATS line from ods-signerd and errors. The Enforcer will run once an hour (or as often you configured it) and you could monitor that output and that you get that each hour.<br>
</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Is it possible to monitor the health of the softhsm?<br></blockquote></div><br></div><div class="gmail_extra">
I'm unsure what you want to monitor here, if there is a problem with the HSM then the Enforcer and/or Signer will report that to the syslog. There is "ods-hsmutil test <repository>" that you might be able to run once a day or something but it does not guarantee that the repository works when it needs to later on.<br clear="all">
</div><div class="gmail_extra"><br></div><div class="gmail_extra">Hope this helps some.<br><br></div><div class="gmail_extra">-- <br>Jerry Lundström - OpenDNSSEC Developer<br><a href="http://www.opendnssec.org/" target="_blank">http://www.opendnssec.org/</a><br>
</div></div>