Minor <Fred Zwarts>
I have set up a system with a new installation of opendnssec-1.4.0a1, which I built from sources on a 64 bit Suse Linux Enterprise System 11 with Service Pack 2.
I added one zone. In the system log I see that this zone is processed and I find the signed zone file.
As this is the first time that this zone is processed, new keys are generated. One of the KSK keys is in the dssub state.
According to the system log the ods-enforcerd executes the DelegationSignerSubmitCommand every hour, since the creation of the key. The name of this command is correct. It is the name of a shell script. However, it looks as if this script is never started. One of the first things that this script does is the creation of a file in the /tmp directory. Even this file is not found.
Running the script from the command line creates this temporary file without problem.
On another system I have opendnssec-1.3 running for a few months, which had no problems to use the same script.
Is there a known problem with the execution of the DelegationSignerSubmitCommand?
If not, how can I diagnose the failure to startup this script?