On Mon, Mar 7, 2022 at 11:22 AM Ulrich Windl < [email protected]> wrote:
> Hi! > > I wrote some services that should run when booting and some time after > booting. > As it seems the service to run during boot works, but the timer-triggered > one > does not. > I have no idea why. > > Here are the details: > # systemctl status prevent-fencing-loop.service > ● prevent-fencing-loop.service - Prevent Pacemaker Fencing-Loop > Loaded: loaded (/usr/lib/systemd/system/prevent-fencing-loop.service; > enabled; vendor preset: disabled) > Active: inactive (dead) since Sat 2022-03-05 10:33:50 CET; 1 day 23h > ago > Docs: man:boot-loop-handler(8) > Main PID: 5226 (code=exited, status=0/SUCCESS) > > Mar 05 10:33:50 h19 systemd[1]: Starting Prevent Pacemaker Fencing-Loop... > Mar 05 10:33:50 h19 boot-loop-handler[5234]: 1 of 4 allowable boots > Mar 05 10:33:50 h19 systemd[1]: prevent-fencing-loop.service: Succeeded. > Mar 05 10:33:50 h19 systemd[1]: Finished Prevent Pacemaker Fencing-Loop. > > So this service ran during boot. > > # systemctl status reset-boot-counter.timer > ● reset-boot-counter.timer - Reset Boot-Counter after 15 minutes > Loaded: loaded (/usr/lib/systemd/system/reset-boot-counter.timer; > enabled; vendor preset: disabled) > Active: inactive (dead) > Trigger: n/a > It's not a problem with any of the [Timer] On* configuration – the problem is that the whole .timer unit isn't active, so its triggers won't get scheduled in the first place. > [Install] > WantedBy=timer.target > The timer is not being scheduled because it's WantedBy a nonexistent target. I think you meant 'timer*s*.target' here. -- Mantas Mikulėnas
