Hi,
I have script in the cron which run at predefined time everyday.
If the script fails then we get the mail and a log is created.
But last night the script didnt run. If the script is even started it creates log so it seems the script never ran. It has never happened before.
Th machine has uptime of 119 days so there was no maintenance on machine.
Does anyone knows where we can check cron logs ..if there is one where its recorded if cron scripts have run or not ???
Thanks in advance
Shipra
Hi,
begin looking in /var/log/cron
tell us what you find there
see ya
fra
Thanks i found the log under /var/adm/cron/log ..i think it should be same
! c queue max run limit reached Thu Dec 15 00:01:00 CST 2011
! rescheduling a cron job Thu Dec 15 00:01:00 CST 2011
Is this error ..this is what i see ... after 13th dec ...
And if its error how to resolve
---------- Post updated at 06:55 AM ---------- Previous update was at 06:27 AM ----------
it seems some user had cron script which was not closing I checked the ppid of cron for processs ... got the process killed and now my cron is workingggg
Thanks a bunch for teh help
Just killing jobs will not solve the issue, you just save time and HP-UX is not PC stuff, some production boxes need maintenance scheduling planified a long time in advance and you have to give very good reason to reboot... (the HP I take care have an uptime if you take off the planned maintenance OR issue ( HW failure...) of above 99.9% and they are not in HA... The planned downtime is about 2 hours per year for all the boxes...).
What I mean is if you haven't found the culprit, it will happen again...
when you looked at PID of cron process, how many processes were running under the same PPID ?
100?
Why are they still running is what you have to solve! cron is waiting for the end of some child process, having cron jobs hanging is not very professional...Some other things you could look at for investigation: Did you have a look at your /var/adm/cron/queuedefs file. How many crontabs files do you have? (in /var/spool/cron/crontabs...)
vbe,
yeh what i meant was we found a script which was the main culprit ..and we are reviewing the script ..it was not closing as a result there were many scripts attached to cron and cron queue got filled ...so now we killed those old opened session and are reviewing that script and meantime other scripts are running fine.
You could change the queues values, but you need a good reason to go that way...
I've seen cases like yours when calling in batch some script written for interactive mode ( press Enter to continue...). Good luck!