👀 Views: 66 💬 Answers: 1 📅 Created: 2025-06-08

debian systemd timer bash

I'm testing a new approach and I'm a bit lost with I'm refactoring my project and I'm having trouble with a systemd timer that I set up on my Debian 11 server..... The timer is supposed to execute a script every hour, but it seems to be running late or not at all. I created a timer unit file in `/etc/systemd/system/my-script.timer` with the following content: ```ini [Unit] Description=Run My Script Every Hour [Timer] OnCalendar=hourly Persistent=true [Install] WantedBy=timers.target ``` My service file for the script located at `/etc/systemd/system/my-script.service` looks like this: ```ini [Unit] Description=My Script Service [Service] Type=oneshot ExecStart=/usr/local/bin/my-script.sh ``` I enabled the timer with `systemctl enable my-script.timer` and started it using `systemctl start my-script.timer`. However, when I check the status with `systemctl list-timers`, it shows the next execution time is always off by a few minutes, and sometimes it doesn't run at all. I also checked the logs with `journalctl -u my-script.service` and see entries like: ``` my-script.service: Executing: /usr/local/bin/my-script.sh my-script.service: Failed to execute command: No such file or directory ``` To troubleshoot, I verified that the script `/usr/local/bin/my-script.sh` exists and is executable (`chmod +x /usr/local/bin/my-script.sh`). I've even tried running the script manually, and it works without issues. Could there be an scenario with the environment in which the timer is executing the script? I've read that timers run in a different environment than user shells, but I'm not sure how to debug this further. Any suggestions on how to fix this or why it's behaving this way? I'm using Bash 3.11 in this project. Thanks for taking the time to read this! I'm working in a Linux environment. Any help would be greatly appreciated! The project is a mobile app built with Bash. Thanks, I really appreciate it!