👀 Views: 193 💬 Answers: 1 📅 Created: 2025-06-01

systemd linux fedora bash

I've searched everywhere and can't find a clear answer. I'm testing a new approach and I've set up a systemd timer to execute a service daily, but after the initial run, it doesn't seem to trigger again. Here's the relevant timer and service files: **/etc/systemd/system/my-service.service** ```ini [Unit] Description=My Sample Service [Service] Type=oneshot ExecStart=/usr/local/bin/my-script.sh ``` **/etc/systemd/system/my-service.timer** ```ini [Unit] Description=Runs My Sample Service Daily [Timer] OnCalendar=daily Persistent=true [Install] WantedBy=timers.target ``` I enabled and started the timer using: ```bash sudo systemctl enable my-service.timer sudo systemctl start my-service.timer ``` The service runs as expected on the first trigger, and I can see the output in the journal using `journalctl -u my-service.service`. However, after that, the timer does not seem to trigger again. I checked with `systemctl list-timers` and it shows the timer as active but doesn't indicate any next trigger. I've also tried inspecting the logs with `journalctl -u my-service.timer` but it only shows the initial trigger event. I suspect there might be an scenario with the timer configuration or how it's handling the `OnCalendar` directive. Any ideas on what might be going wrong or how I can troubleshoot this further? I'm working with Bash in a Docker container on CentOS. I'd love to hear your thoughts on this.