check whether lots of queue waiting for execution with cron. Like somebody had done mistake that every minute the backup job will run and the job was around 10gb. So before ending the one cron other will start immediately and will be in spool dir. So please check for something like this. May help ful to you. Then check the spool dir in /var. On 12/26/06, inode0 <inode0@xxxxxxxxx> wrote:
On 12/26/06, Bill Tangren <bjt@xxxxxxxxxxxxxxxx> wrote: > I have one server on which it does not seem that the cron daemon is working. I > use cron to do system backups and to rotate those backups (as well as quite a > few other things). None of them seem to be happening. > > My question is, what do I look for in the logs to determine whether or not the > cron daemon is running, and if not, why not? # chkconfig --list crond crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off # service crond status crond (pid 3311) is running... /var/log/cron may be helpful. John -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
-- Nilesh Vaghela ElectroMech Redhat Channel Partner and Training Partner 74, Nalanda Complex, Satellite Rd, Ahmedabad 25, The Emperor, Fatehgunj, Baroda. www.electromech.info -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
