-
Type:
Bug
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 2.1.10
-
Fix Version/s: None
-
Component/s: Signer
-
Labels:None
-
Environment:
Linux
On my system - embedded, slow I/O fast CPU I get the following:
{{Feb 13 02:14:25 p0 local0.warn ods-signerd: WARNING: unable to sign zone example.com.com, signconf is not ready
Feb 13 02:14:25 p0 local0.err ods-signerd: [file] unable to stat file /mnt/opendnssec/signconf/example.com.com.xml: ods_fopen(
Feb 13 02:14:25 p0 local0.warn ods-signerd: WARNING: unable to sign zone example.com.com, signconf is not ready
...
Feb 13 02:14:25 p0 local0.err ods-signerd: [file] unable to stat file /mnt/opendnssec/signconf/example.com.com.xml: ods_fopen(
Feb 13 02:14:25 p0 local0.warn ods-signerd: WARNING: unable to sign zone example.com.com, signconf is not ready
}}
maybe a thousand times - for each zone that is added
Suggest that the backoff time be non-zero in ./common/scheduler/task.c
{{ --- ./common/scheduler/task.o 2022-02-13 02:49:20.576081442 +0000
+++ ./common/scheduler/task.c 2022-02-13 02:21:44.789541440 +0000
@@ -134,6 +134,9 @@
rescheduleTime = 0;
} else if (rescheduleTime == schedule_DEFER) {
task->backoff = clamp(task->backoff * 2, 60, ODS_SE_MAX_BACKOFF);
+ if(task->backoff == 0)
ods_log_info("back-off task %s for zone %s with %lu seconds", task->type, task->owner, (long) task->backoff);
rescheduleTime = time_now() + task->backoff;
}
}}