I had a daily clamscan running from my user crontab, which stopped running after May update. After perusing man cron, I’ve added -p to cron command in /usr/lib/systemd/system/cronie.service, in hopes that will solve the issue. Will know tomorrow!
Create a simple cron job to create a file in your home at specific time (in two minutes for example). This way you can check if cron works.
Yep, that worked. So I’m puzzled why my nightly job failed, unless cron won’t honor user crontabs without -p (which I didn’t have prior to update, to my knowledge).
OK so maybe this is a X/Y problem. You say cron is broken. Maybe it is your command or script which is. Anyway you will see tomorrow if you cronjob that didnt work before now works with -p… or maybe you can remove your modification to the service, and schedule again the simple command to check if cron just works, which could confirm your other cron job script/command is broken.
My bad. It isn’t crontab, but my postfix. My nightly job sends email with results, but no email doesn’t mean cron broken (duh). Anyway, after some fuss I have gotten postfix working again. It was due to postfix no longer supporting the ‘hash’ dictionary type. I had to migrate over to ‘lmdb’.
Apologies for false start, and thanks for your advice.
1 Like
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.