[Letsencrypt-devel] Bug#831644: certbot failing from cron

Daniel Pocock daniel at pocock.pro
Mon Jul 18 06:55:16 UTC 2016


Package: certbot
Version: 0.8.0-1~bpo8+2
Severity: important


When no certificate needs to be renewed, the cron job runs without error

When there are one or more certificates to be renewed, the job send an
email containing errors:


2016-07-18 00:43:04,562:WARNING:certbot.renewal:Attempting to renew cert
from /etc/letsencrypt/renewal/example.net.conf produced an unexpected
error: The apache plugin is not working; there may be problems with your
existing configuration.
The error was: NoInstallationError(). Skipping.

The following certs are not due for renewal yet:
  /etc/letsencrypt/live/example.org/fullchain.pem (skipped)
  ...
All renewal attempts failed. The following certs could not be renewed:
  /etc/letsencrypt/live/example.net/fullchain.pem (failure)
  ...
2 renew failure(s), 0 parse failure(s)



The job failed two days in a row.

I logged in and ran "certbot -q" manually and it completed without an
error.  Maybe there is something missing from the path in the cron job.

My /etc/cron.d/certbot contains:


# Upstream recommends attempting renewal twice a day
#
# Eventually, this will be an opportunity to validate certificates
# haven't been revoked, etc.  Renewal will only occur if expiration
# is within 30 days.
0 */12 * * * root perl -e 'sleep int(rand(3600))'; certbot -q renew



More information about the Letsencrypt-devel mailing list