implementing Systemd Timer Not Triggering on Fedora 36
I'm trying to debug I'm a bit lost with I'm trying to set up a systemd timer on my Fedora 36 machine to run a backup script every day at 2 AM, but it doesn't seem to trigger as expected. I've created the service file and the timer file, and they are both enabled and started, but the backup script isn't running. Here are the contents of both files: **Backup Service File (`/etc/systemd/system/backup.service`):** ```ini [Unit] Description=Daily Backup Service [Service] Type=oneshot ExecStart=/usr/local/bin/backup_script.sh ``` **Timer File (`/etc/systemd/system/backup.timer`):** ```ini [Unit] Description=Run Daily Backup [Timer] OnCalendar=*-*-* 02:00:00 Persistent=true [Install] WantedBy=timers.target ``` I ran `systemctl list-timers` to check if the timer is active, and it shows up correctly. The output is: ``` NEXT LEFT LAST PASSED UNIT ACTIVATES Tue 2023-10-31 02:00:00 UTC 15min left n/a n/a backup.timer backup.service ``` But when I check the logs using `journalctl -u backup.service`, I see no entries indicating that the service ran at all. The `backup_script.sh` is executable and works when I run it manually. I've tried reloading the systemd manager configuration with `systemctl daemon-reload` and restarting the timer with `systemctl restart backup.timer`, but the scenario continues. I'm also running `systemd` version 250.4. Is there something I might be missing in the configuration? Any tips for debugging what might be going wrong? This is for a CLI tool running on Ubuntu 22.04. Thanks for any help you can provide! How would you solve this?