Thanks, I looked into that now:
$ grep letsencrypt.cron /var/log/cron
Sep 2 03:13:13 one run-parts(/etc/cron.daily)[15199]: starting
letsencrypt.cron
Sep 2 03:13:13 one run-parts(/etc/cron.daily)[15747]: finished
letsencrypt.cron
Sep 3 03:19:14 one run-parts(/etc/cron.daily)[9936]: starting
letsencrypt.cron
Sep 3 03:19:15 one run-parts(/etc/cron.daily)[10466]: finished
letsencrypt.cron
Sep 4 03:13:13 one run-parts(/etc/cron.daily)[21800]: starting
letsencrypt.cron
Sep 4 03:13:13 one run-parts(/etc/cron.daily)[22321]: finished
letsencrypt.cron
This repeats down to August 19th (furthest back I have cron logs for
this entry)
So, it doesn't look like cron or the daily scripts are the culprit.
- Brent
On 2019-09-03 17:37, Greg Kuhnert wrote:
I found one trap a while back. This cron job is in cron.daily … If you have
another cron job that is daily that hangs, the system will stop running other
daily jobs till that one is fixed. Check any stuck cron jobs - that might be a
possible cause.
GK
On 4 Sep 2019, at 8:01 am, Michael Stauber <mstau...@blueonyx.it> wrote:
Hi Brent,
I had a site fail auto-renewal today. Renewed by hand through the BX GUI
and worked fine.
The only relevant entries in the LE logs were from the initial cert
generation/lease and the manual renew I just performed.
If it the cert was expired it would mean that the daily cronjob would
have tried to renew it daily - for the last 30 days. Or possibly crond
didn't run or one of the CODB flags that would include that cert in the
renewal run wasn't set. Hard to say after the fact.
--
With best regards
Michael Stauber
_______________________________________________
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx
_______________________________________________
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx
_______________________________________________
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx
