Bug#1033548: 02:00 timers dont run in DST transition night

[Michael Biebl]

Control: tags -1 + moreinfo

Hi Marc

On Mon, 27 Mar 2023 11:29:32 +0200 Marc Haber 
<mh+debian-packages at zugschlus.de> wrote:
> Package: systemd
> Version: 252.6-1
> Severity: minor
> 
> Hi,
> 
> aide-common ships the following timer:
> 
> [Unit]
> Description=Daily AIDE check
> 
> [Timer]
> OnCalendar=*-*-* 02:00:00
> RandomizedDelaySec=2h
> Persistent=true
> 
> [Install]
> WantedBy=timers.target
> 
> This didn't run in DST transition night. I think this might be caused by
> the clock jumping from 01:59 to 03:00, with 02:00 not existing.
> 
> Is there a notation to have a systemd timer run even if the exact time
> the timer is supposed to run doesn't happen? I guess this might also be
> the case in case of a grossly misticking clock and a timesync daemon
> stepping the time, for example, from 01:59:50 to 02:02:00?
> 
> Or would be probably be a better idea to trigger a timer if systemd
> finds the trigger time in the past without the timer having been
> triggered?
> 
> Not running at all came as kind of surprise for me.
> 
> I might be holding things wrong but I'd like your opinion.

What was/is the output of
systemctl list-timers
before and after such a (DST) time jump?

I.e., is there a way to reproduce this somehow?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20230826/1a2e7ffa/attachment.sig>