I have a very simple .service file that runs a Bash script, and is tied to a .timer with an identical name.
I'm debugging the failure of the .timer to activate the .service file, but the immediate issue is that
sudo systemctl start p.service
fails to activate the .service file (meaning, run the Bash script), while
sudo systemctl restart p.service
activates the .service file successfully, running the Bash script, just fine.
The question is, why? I imagine this may relate to the failure of the .timer to activate the .service file but perhaps not.
- The Bash script runs independently specifying the full path to it.
- The timer's OnCalendar= specification passes inspection using systemd-analyze calendar.
- Permissions are correct (700 for the script, 644 for the units).