I have found it not unknown for crond to just die, especially on SMP machines. I used to have 2 machines identical to each other except one had only 1 single CPU, when I added another cu, drond started dying just like the smp machine. Also another reason cron can die is if you have a password expiry on root, I have only seen this on Sun boxes mind you I have never set a expiry on Linux. Regards Steven -----Original Message----- From: Darryl W. DeLao Jr. [mailto:ddelao@xxxxxxxxx] Sent: Tuesday, 26 April 2005 1:08 p.m. To: redhat-list@xxxxxxxxxx Subject: Cron Job Failure For some reason, one of my servers has decided to stop running all of its scheduled cron jobs. The cron jobs are still listed and configured correctly based on the commands to run, times, etc but none of them run. They have been running fine now for well over 6 months. The only thing that I can think of as to why they stopped running was some RedHat updates that I applied last week. All log files on the server indiciate that the last time the cron jobs ran was on 4/16, which is the day I applied the updates. The problem however gets better, because I have 4 other servers which are exactly like this one and they got the updates as well and their cron jobs run just fine. Just curious if anyone else is having this problem and what have you done about it? Also, how can I get my cron jobs working again? Do I have to re-create each one? Some were there by system default. Thanks for any help in advance, Darryl -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
