On 2026-04-13 14:06:23 +0200, Vincent Lefevre wrote: > This is indeed the case. The anacron(8) man page says: > > After the command exits, Anacron records the date in a > special timestamp file for that job, so it can know when > to execute it again. Only the date is used for the time > calculations. The hour is not used. > > So I got the issue on the first machine because I upgraded > between midnight and about 7:30.
On January 8, I also upgraded anacron between midnight and about 7:30 (on the same machine), but the configure of anacron did not freeze: Jan 08 01:17:41 qaa systemd[1]: Started anacron.service - Run anacron jobs. Jan 08 01:17:41 qaa systemd[1]: anacron.timer: Deactivated successfully. Jan 08 01:17:41 qaa systemd[1]: Stopped anacron.timer - Trigger anacron every hour. Jan 08 01:17:41 qaa systemd[1]: Stopping anacron.timer - Trigger anacron every hour... Jan 08 01:17:41 qaa systemd[1]: Started anacron.timer - Trigger anacron every hour. Jan 08 01:17:41 qaa anacron[271550]: Anacron 2.3 started on 2026-01-08 Jan 08 01:17:41 qaa anacron[271550]: Will run job `cron.daily' in 5 min. Jan 08 01:17:41 qaa anacron[271550]: Jobs will be executed sequentially [...] Jan 08 01:22:41 qaa anacron[271550]: Job `cron.daily' started Jan 08 01:22:41 qaa anacron[274056]: Updated timestamp for job `cron.daily' to 2026-01-08 Jan 08 01:22:42 qaa anacron[271550]: Job `cron.daily' terminated Jan 08 01:22:42 qaa anacron[271550]: Normal exit (1 job run) Jan 08 01:22:42 qaa systemd[1]: anacron.service: Deactivated successfully. Jan 08 01:22:42 qaa systemd[1]: anacron.service: Consumed 714ms CPU time, 92.7M memory peak. and /var/log/dpkg.log.3.gz shows that this did not freeze: 2026-01-08 01:17:41 configure anacron:amd64 2.3-47 <none> 2026-01-08 01:17:41 status unpacked anacron:amd64 2.3-47 2026-01-08 01:17:41 status half-configured anacron:amd64 2.3-47 2026-01-08 01:17:41 status installed anacron:amd64 2.3-47 To be compared with /var/log/dpkg.log: 2026-04-12 01:04:00 configure anacron:amd64 2.3-48 <none> 2026-04-12 01:04:00 status unpacked anacron:amd64 2.3-48 2026-04-12 01:04:00 status half-configured anacron:amd64 2.3-48 2026-04-12 01:14:01 status installed anacron:amd64 2.3-48 Here one can see a 10-minute delay before the configure of anacron terminated. So this seems to be a regression. -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
