Hi,
I am seeing the exact same behavior on my system running raspian 9,
certbot 0.28.0-1~deb9u1 with apache. My letsencrypt certificate almost
expired because of it. Is there a workaround? "sudo systemctl start
certbot.timer" appears to have restarted the timer, but I am not sure it
is stable upon reboot.
Thanks,
David
On Tue, 12 Feb 2019 08:56:02 +0100 =?iso-8859-1?Q?V=E1clav_Ovs=EDk?=
<vaclav.ov...@gmail.com> wrote:
> Hello Harlan,
>
> On Mon, Feb 11, 2019 at 06:45:46PM -0500, Harlan Lieberman-Berg wrote:
> > ...
> >
> > Hello Václav,
> >
> > Hm, that's strange. I went back and checked, and the timer file was
> > present in the 0.10 version as well. The timer used to work, and now
> > no longer does, correct?
>
> Exactly. I speak to colleague and he is also affected on one machine.
>
> > Can you send the output of `systemctl show certbot.timer`?
>
> attached...
> I left the thing as is on one server (anketa). The timer is still
> inactive...
>
> anketa:~# systemctl list-timers --all
> NEXT LEFT LAST PASSED UNIT ACTIVATES
> Tue 2019-02-12 08:39:00 CET 4min 18s left Tue 2019-02-12 08:09:01 CET
25min ago phpsessionclean.timer phpsessionclean.service
> Tue 2019-02-12 09:10:54 CET 36min left Mon 2019-02-11 20:36:35 CET
11h ago apt-daily.timer apt-daily.service
> Tue 2019-02-12 20:30:40 CET 11h left Mon 2019-02-11 20:30:40 CET 12h
ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service
> Wed 2019-02-13 06:11:23 CET 21h left Tue 2019-02-12 06:39:20 CET 1h
55min ago apt-daily-upgrade.timer apt-daily-upgrade.service
> n/a n/a Tue 2019-01-29 00:18:30 CET 2 weeks 0 days ago certbot.timer
certbot.service
>
> 5 timers listed.
>
> anketa:/var/log/letsencrypt# ll -lrt /var/log/letsencrypt/ | tail -15
> -rw-r--r-- 1 root root 642 Jan 26 00:42 letsencrypt.log.12
> -rw-r--r-- 1 root root 642 Jan 26 12:58 letsencrypt.log.11
> -rw-r--r-- 1 root root 642 Jan 27 00:01 letsencrypt.log.10
> -rw-r--r-- 1 root root 642 Jan 27 12:44 letsencrypt.log.9
> -rw-r--r-- 1 root root 642 Jan 28 00:06 letsencrypt.log.8
> -rw-r--r-- 1 root root 973 Jan 28 10:09 letsencrypt.log.7
> -rw-r--r-- 1 root root 17371 Jan 28 10:09 letsencrypt.log.6
> -rw-r--r-- 1 root root 2976 Jan 28 10:13 letsencrypt.log.5
> -rw-r--r-- 1 root root 10862 Jan 28 10:13 letsencrypt.log.4
> -rw-r--r-- 1 root root 24656 Jan 28 10:15 letsencrypt.log.3
> -rw-r--r-- 1 root root 26076 Jan 28 10:16 letsencrypt.log.2
> -rw-r--r-- 1 root root 642 Jan 28 12:26 letsencrypt.log.1
> -rw-r--r-- 1 root root 297 Jan 29 00:18 letsencrypt.log-20190203.gz
> -rw-r--r-- 1 root root 20 Feb 3 06:25 letsencrypt.log-20190210.gz
> -rw-r--r-- 1 root root 0 Feb 10 06:25 letsencrypt.log
>
>
> As the certbot was not run anymore, logrotate started to rotate
> letsencrypt.log file. I have logrotate configured to use dateext to not
> fulfill incremental backups with cruft. Renamed logfile series are
> backed-up repeatedly... With date extension they are static and go to
> backup only one times.
> BTW: certbot with its thousand files is a bit inconvenient. Every time
> certbot runs, it rotates all thousand files, so they all go to backup
> everyday. This is upstream problem probably...
>
> The times of some of the above logfiles are from Jan 28, because I
was solving
> a change of the LE authentication method.
>
> Thanks for your time and effort
--
**********************************
David M. Kaplan
Charge de Recherche 1
Institut de Recherche pour le Developpement (IRD)
UMR MARBEC (IRD/Ifremer/CNRS/UMII)
av. Jean Monnet
CS 30171
34203 Sete cedex
France
Email: david.kap...@ird.fr
Phone: +33 (0)4 99 57 32 25
Fax: +33 (0)4 99 57 32 95
http://www.umr-marbec.fr/kaplan-david.html
http://www.davidmkaplan.fr/
**********************************
