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
--
Zito
Unit=certbot.service
NextElapseUSecRealtime=infinity
NextElapseUSecMonotonic=infinity
LastTriggerUSec=49y 3w 6d 17h 18min 30.552506s
LastTriggerUSecMonotonic=1w 3d 4h 8min 41.634499s
Result=success
AccuracyUSec=1min
RandomizedDelayUSec=12h
Persistent=yes
WakeSystem=no
RemainAfterElapse=yes
Id=certbot.timer
Names=certbot.timer
Requires=-.mount sysinit.target var.mount
WantedBy=timers.target
Conflicts=shutdown.target
Before=shutdown.target certbot.service timers.target
After=-.mount time-sync.target sysinit.target var.mount
Triggers=certbot.service
RequiresMountsFor=/var/lib/systemd/timers
Description=Run certbot twice daily
LoadState=loaded
ActiveState=inactive
SubState=dead
FragmentPath=/lib/systemd/system/certbot.timer
UnitFileState=enabled
UnitFilePreset=enabled
StateChangeTimestamp=Tue 2019-01-29 08:14:17 CET
StateChangeTimestampMonotonic=907468902955
InactiveExitTimestamp=Fri 2019-01-18 20:10:53 CET
InactiveExitTimestampMonotonic=64450831
ActiveEnterTimestamp=Fri 2019-01-18 20:10:53 CET
ActiveEnterTimestampMonotonic=64450831
ActiveExitTimestamp=Tue 2019-01-29 08:14:17 CET
ActiveExitTimestampMonotonic=907468902955
InactiveEnterTimestamp=Tue 2019-01-29 08:14:17 CET
InactiveEnterTimestampMonotonic=907468902955
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
NeedDaemonReload=no
JobTimeoutUSec=infinity
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Fri 2019-01-18 20:10:53 CET
ConditionTimestampMonotonic=64239605
AssertTimestamp=Fri 2019-01-18 20:10:53 CET
AssertTimestampMonotonic=64239605
Transient=no
Perpetual=no
StartLimitIntervalSec=10000000
StartLimitBurst=5
StartLimitAction=none
InvocationID=242ece5a59404f9ea996e16b505f3aa4
