systemd service not being triggered by its timer unit

Question

Here is my service unit definition

[Unit]
Description=My Service

[Service]
ExecStart=/bin/bash -lc /usr/local/bin//myservice
# ExecStop=/bin/kill -15 $MAINPID
EnvironmentFile=/etc/myservice/config
User=myuser
Group=mygroup

and its timer unit file

[Unit]
Description=Timer for myservice

[Timer]
Unit=myservice.service
OnCalendar=*-*-* 10:33:00

[Install]
WantedBy=timers.target

I have tentatively set the OnCalendar to *-*-* 10:33:00 (followed by a sudo systemctl daemon-reload) but as a I was watching my machine, I didn't see the service firing. I had also set it for 5AM but this morning I saw no evidence of execution

When I perform a manual sudo systemctl start myservice it works as expected.

What might be preventing the service from executing according to its timer schedule?

So what does `systemctl list-timers` output? It tells when it will execute. — KamilCuk, Nov 14 '21 at 10:59
You are right, it is not listed there! Any idea how can I dig deeper into why? — pkaramol, Nov 14 '21 at 11:14
You did not start the timer. `sudo systemctl start myservice.timer` — KamilCuk, Nov 14 '21 at 11:14
wish I could throw a facepalm emoji here. thanks; post it as an answer so that I can accept it you'd like — pkaramol, Nov 14 '21 at 11:15

score 1 · Accepted Answer · answered Nov 14 '21 at 11:19

1

You did not start the timer.

sudo systemctl start myservice.timer

answered Nov 14 '21 at 11:19

KamilCuk

120,984
8
59
111

systemd service not being triggered by its timer unit

1 Answers1