I’ve just brought a new server online and configured it the way the old one was regarding cron, but the jobs aren’t running. So, I went through the configuration carefully and checked that the current cron works the way the old one did. Yes, it appears so!
As it’s a “systemd” type system, I ran the appropriate command to see what it thinks is scheduled, and here’s what I got:
# systemctl list-timers --all NEXT LEFT LAST PASSED UNIT ACTIVATES Sun 2020-08-16 15:15:55 PDT 5min left Sun 2020-08-16 14:15:54 PDT 54min ago dnf-makecache.timer dnf-makecache.service Sun 2020-08-16 20:57:26 PDT 5h 47min left Sat 2020-08-15 20:57:26 PDT 18h ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service Mon 2020-08-17 00:00:00 PDT 8h left Mon 2020-08-10 00:00:00 PDT 6 days ago fstrim.timer fstrim.service Mon 2020-08-17 00:00:00 PDT 8h left Sun 2020-08-16 00:00:01 PDT 15h ago mlocate-updatedb.timer mlocate-updatedb.service Mon 2020-08-17 00:00:00 PDT 8h left Sun 2020-08-16 00:00:01 PDT 15h ago unbound-anchor.timer unbound-anchor.service 5 timers listed.
That’s all well and good, but it’s not showing my specific additions – any of them. So, I did what I thought was correct, I ran
systemctl reload crond.service and got the same output. So I restarted and still got the same output!
My additions are:
- cron.d: local – a set of local things that aren’t on the usual schedules
- cron.daily: backup.daily logrotate mailbox_check
- cron.monthly; backup.monthly, and;
- cron.weekly; backup.weekly
I’m fully prepared to believe I did something wrong in the config, or maybe there’s some other issue on why I don’t THINK they ran but they did. But I’m not seeing the other entries in the
systemctl list-timers output that were put there by installed packages that were there before I even started mucking with my own additions.
Perhaps the problem is my unfamiliarity with the list-timer output? Is it not supposed to show these other jobs, too?