Function md_job_delay_on_errors

modules/md/md_status.c:633–670

}

apr_time_t md_job_delay_on_errors(md_job_t *job, int err_count, const char *last_problem)
{
    apr_time_t delay = 0, max_delay = apr_time_from_sec(24*60*60); /* daily */
    unsigned char c;

    if (last_problem && md_acme_problem_is_input_related(last_problem)) {
        /* If ACME server reported a problem and that problem indicates that our
         * input values, e.g. our configuration, has something wrong, we always
         * go to max delay as frequent retries are unlikely to resolve the situation.
         * However, we should nevertheless retry daily, bc. it might be that there
         * is a bug in the server. Unlikely, but... */
        delay = max_delay;
    }
    else if (err_count > 0) {
        /* back off duration, depending on the errors we encounter in a row.
         * As apr_time_t is signed, this might wrap around*/
        int i;
        delay = job->min_delay;
        for (i = 0; i < (err_count - 1); ++i) {
          delay <<= 1;
          if ((delay <= 0) || (delay > max_delay)) {
              delay = max_delay;
              break;
          }
        }
    }
    if (delay > 0) {
        /* jitter the delay by +/- 0-50%.
         * Background: we see retries of jobs being too regular (e.g. all at midnight),
         * possibly cumulating from many installations that restart their Apache at a
         * fixed hour. This can contribute to an overload at the CA and a continuation
         * of failure.
         */
        md_rand_bytes(&c, sizeof(c), job->p);
        delay += apr_time_from_sec((apr_time_sec(delay) * (c - 128)) / 256);
    }
    return delay;
}

void md_job_end_run(md_job_t *job, md_result_t *result)
{