Operating System - Tru64 Unix
1748123 Members
3323 Online
108758 Solutions
New Discussion юеВ

Re: cronjob did not start

 
SOLVED
Go to solution
Tim Martens_1
New Member

cronjob did not start

Hi,

I had a problem with cron yesterday. A cronjob to backup the oracle database did not start. The crontab of the oracle user was not modified, and the /var/adm/cron/log file shows no errors at that time.

crontab line from oracle:
30 17 * * 1-5 $HOME/bin/db_rman_backup -l 1 -x 6 -t ARG_PR1 >> $HOME/log/ARG_PR1/onlbck.log 2>&1 || $HOME/bin/mail_backup

cron log file:
! *** cron started *** pid = 525564 Fri May 30 23:55:38 2003
! Max job limit set to 25 jobs Fri May 30 23:55:38 2003
! Log level set to 4 Fri May 30 23:55:38 2003
! *** cron exiting on signal 15 *** pid = 525564 Thu Jun 12 18:26:30 2003
! *** cron started *** pid = 525479 Thu Jun 12 18:34:44 2003
! Max job limit set to 25 jobs Thu Jun 12 18:34:44 2003
! Log level set to 4 Thu Jun 12 18:34:44 2003

(The line containing the cron exit is in the log file because I had to reboot the server at 18:20 - This has nothing to do with the cron problem)

We're running tru64 V5.1a

Any help would be appreciated.
Thanks,
Tim Martens
6 REPLIES 6
Ian Lochray
Respected Contributor

Re: cronjob did not start

Tim,
does uerf report any errors prior to the cronjob scheduled start time i.e. disk space errors etc.?

Re: cronjob did not start

Tim,
Is this a new script or something that has worked for some time?

Did this only happen once?

The the log file you append to get updated?

Is the time and date correct on the machine?

Are all files that need to be executable exectuable?

You may want to put your script in debug mode (ksh -x) and run it that way.

What shell does your script use?

Hope this helps,

Christian Klein
Caesar_3
Esteemed Contributor

Re: cronjob did not start

Hello!

Does your cron deamon run?
Is this new task for cron or you alredy run this in the past?

Caesar
Alexey Borchev
Regular Advisor
Solution

Re: cronjob did not start

Maybe, Your Cron daemon does not run or run TWICE?
(I had an experience. Together they are working ... strange!)

I would try to submit some jobs to cron (for example, touch /tmp/myfile)

and start/stop cron - it's better to do:
/sbin/rc3.d/S57cron stop
/sbin/rc3.d/S57cron start

In case You will not resolve issue withing one day, it's possible to run:
sleep ; backup_script

(Just to avoid running backup manually at 3.00 AM)
The fire follows shedule...
Tim Martens_1
New Member

Re: cronjob did not start

Hi,

We had a problem with cron on all 3 members of our cluster.
uerf didn't show any errors. There were NO modifications (not in the cronjobs, not in the ksh script ).
Stopping and starting the cron daemon did do the job. (It's still strange that all 3 cron daemons on all 3 members of the cluster 'hang' without any errors ).
Hopefully it is a one-time problem.

Thanks all for the response.

Tim.
Michael Schulte zur Sur
Honored Contributor

Re: cronjob did not start

In /var/adm/cron you'll find a file called queuedefs with a line max_jobs=25.
This explains the warning you received.
Increase it and restart the cron daemon.

Hope, I could help

Michael Schulte