On Sun, 2006-09-03 at 14:31 +0200, Anders Johansson wrote:
On Sunday 03 September 2006 14:12, Rick Friedman wrote:
Below is a copy of a crontab which should have run this morning. The times have been changed several times this morning trying to figure out what is happening:
# dar backup of / partition 30 0 * * 6 /root/full_system_dar_backup.sh
# dar backup of /home partition 10 13 * * 6 /root/full_home_dar_backup.sh
30 0 * * 1,2,3,4,5,7 /root/diff_system_dar_backup.sh
55 7 * * 1,2,3,4,5,7 /root/diff_home_dar_backup.sh
This also happening with the cron jobs of regular users.
Do you get any messages in /var/log/messages when a job is meant to run?
Can you run the problematic scripts manually?
did this ever work through cron?
Running these scripts manually works fine. It's not just these scripts which are not being executed but those of other users as well. As for messages in /var/log/messages, at 00:30 today, a message shows that cron ran the above task /root/diff_system_dar_backup.sh: Sep 3 00:30:01 chisum /usr/sbin/cron[6109]: (root) CMD (/root/diff_system_dar_backup.sh) At 7:55, when the task /root/diff_home_dar_backup.sh should've run, the only message that appears is: Sep 3 07:55:01 chisum /usr/sbin/cron[4557]: (root) RELOAD (tabs/root) These tasks had been running fine through cron until this morning. I've tried restarting cron several times. I've also rebooted but to no avail.