On Sat, Aug 21, 2021 at 02:12:14PM -0400, Robert Edmonds wrote: > Hi, > > systemd-cron's cron targets fail without being able to invoke > /bin/run-parts, e.g.: > > ● cron-daily.service - systemd-cron daily script service > Loaded: loaded (/lib/systemd/system/cron-daily.service; static) > Active: failed (Result: exit-code) since Sat 2021-08-21 06:25:03 > EDT; 41ms ago > Docs: man:systemd.cron(7) > Process: 833540 ExecStartPre=/lib/systemd-cron/boot_delay 5 > (code=exited, status=0/SUCCESS) > Process: 833541 ExecStart=/bin/run-parts --report /etc/cron.daily > (code=exited, status=203/EXEC) > Main PID: 833541 (code=exited, status=203/EXEC) > CPU: 27ms > > Aug 21 06:25:03 chase systemd[1]: Starting systemd-cron daily script > service... > Aug 21 06:25:03 chase systemd[833541]: cron-daily.service: Failed to > locate executable /bin/run-parts: No such file or directory > Aug 21 06:25:03 chase systemd[833541]: cron-daily.service: Failed at step > EXEC spawning /bin/run-parts: No such file or directory > Aug 21 06:25:03 chase systemd[1]: cron-daily.service: Main process > exited, code=exited, status=203/EXEC > Aug 21 06:25:03 chase systemd[1]: cron-daily.service: Failed with result > 'exit-code'. > Aug 21 06:25:03 chase systemd[1]: Failed to start systemd-cron daily > script service. > Aug 21 06:25:03 chase systemd[1]: cron-daily.service: Triggering > OnFailure= dependencies.
It looks like systemd-cron is hard-coding the path to run-parts in two places: * cron-boot.service * cron-schedule.service If this gets fixed, debianutils can add a Breaks for the appropriate version of systemd-cron.
