Hi Harlan, Thanks for looking at this. I'm running systemd 247 (247.3-7+deb11u1) on Debian GNU/Linux 11 (bullseye)
`systemctl list-timers` shows: ``` NEXT LEFT LAST PASSED UNIT ACTIVATES ... Mon 2023-05-01 20:22:13 BST 2 weeks 0 days left Sat 2023-04-01 20:22:13 BST 2 weeks 1 days ago certbot.timer certbot.service 8 timers listed. Pass --all to see loaded but inactive timers, too. ``` Importantly: 2 weeks ago, 2 weeks left. Is my `certbot.timer` out of date? Mine includes `OnCalendar=*-*-01 20:22:13`. I don't have any `.dpkg-dist` or `.dpkg-old` versions on the machine. For what it's worth, I've been using Certbot on this machine since before it was a Debian package, I think. The machine has been through 2–3 Debian upgrades, and `certbot.timer` has a modify time of 2017-07-19. Would you recommend deleting everything Certbot-related except `/etc/letsencrypt` and then reinstalling the APT package? Sorry – I thought APT or dpkg would have thrown an error if they'd run into file conflicts. Thank-you ---- On Sun, 16 Apr 2023 05:15:42 +0000 Harlan Lieberman-Berg wrote --- > tag 1034325 +moreinfo > thanks > > On Thu, Apr 13, 2023 at 12:54 AM Blieque hims...@blieque.co.uk> wrote: > > The (legacy?) Cron job (`/etc/cron.d/certbot`) for Certbot runs the > > certificate renewal program every 12 hours, and starts with a random > > 0–12-hour delay. This helps to distribute load on Let's Encrypt servers > > over time. > > Hi there, > > Are you sure that it's not triggering twice daily? The systemd timer > with OnCalendar running twice a day has been in Debian since certbot > 0.23, which went into stretch. > > What version of systemd are you running on this host? Can you show me > the relevant line from `systemctl list-timers`? > > Sincerely, >
