systemd anacron.service problem, runs only once after boot

[gene heskett]

On 8/11/24 08:20, Sam Varshavchik wrote:
> Chris Green writes:
> 
>> My cron.daily tasks (the executables in /etc/cron.daily) are only ever
>> getting run once after a system boot.  Up until July 22nd (I'm not
>> sure if that date is significant) they all ran, as designed, every day,
>>
>> What I see from systemctl is:-
>>
>>     chris at q957$ date
>>     Sun Aug 11 09:10:34 AM BST 2024
>>     chris at q957$ systemctl status anacron.service
>>     ○ anacron.service - Run anacron jobs
>>          Loaded: loaded (/usr/lib/systemd/system/anacron.service; 
>> enabled; preset: enabled)
>>          Active: inactive (dead) since Mon 2024-08-05 11:11:07 BST; 5 
>> days ago
>>        Duration: 10min 3.217s
>>            Docs: man:anacron
>>                  man:anacrontab
>>        Main PID: 696 (code=exited, status=0/SUCCESS)
>>             CPU: 3.441s
> 
> Comparing this to what I show, systemctl also shows one more data point 
> for me:
> 
> TriggeredBy: ● anacron.timer
> 
> root at ripper:~# locate anacron.timer
> /etc/systemd/system/timers.target.wants/anacron.timer
> /usr/lib/systemd/system/anacron.timer
> /var/lib/systemd/deb-systemd-helper-enabled/anacron.timer.dsh-also
> /var/lib/systemd/deb-systemd-helper-enabled/timers.target.wants/anacron.timer
> /var/lib/systemd/timers/stamp-anacron.timer
> 
> 
> /lib/systemd/system/anacron.timer is installed by the anacron package. 
> Check that it's installed, if so: "systemctl enable anacron.timer".
> 
Sounds like this last lines advice would be the next logical step to take.

Cheers, Gene Heskett, CET.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis