Home / server / Questions / 782407
In Process
meilon
Asked: 2016-06-08 00:42:38 +0800 CST

Systemd timer ignoring multipe hours

  • 772

on an Arch linux machine hosting an nginx I want to automatically renew its LetsEncrypt certificates. I wrote a .service and .timer for this:

#letsencrypt-update.service
[Unit]
Description=LetsEncrypt Update Service

[Service]
Type=oneshot
ExecStart=/usr/bin/letsencrypt renew --quiet


#letsencrypt-update.timer
[Unit]
Description=LetsEncrypt Update Timer

[Timer]
OnCalendar=03,21:22
Persistent=true

[Install]
WantedBy=basic.target

Per certbot documentation the LetsEncrypt update should be run twice a day, an per systemd.time documentation it should be possible to run the service at 03:22 and 21:22 by separating the hours by comma, but when I reenable the timer, the next execution in systemctl list-timers is on 03:22 and not 21:22 (it's 10 am here).

Why is that? Does systemd has to run the 03:22 timer before it executes the 21:22 one?

arch-linux systemd lets-encrypt

2 Answers

  1. I use OnUnitActiveSec=12h to renew every 12 hours. Here's my full certbot-renewal.timer:

    [Unit]
Description=Timer for Certbot Renewal

[Timer]
OnBootSec=300
OnUnitActiveSec=12h

[Install]
WantedBy=multi-user.target
    • 1

  2. The original configuration of Meilon seems to be ok. But I would use this as timer config:

    #letsencrypt-update.timer
[Unit]
Description=LetsEncrypt Update Timer
PartOf=%p.service

[Timer]
OnCalendar=03,21:22
RandomizedDelaySec=600
Persistent=true

[Install]
WantedBy=basic.target
    • 0