Scheduled conjobs do not run

[Indira Aramandla]

Hi,

We scheduled few cron jobs which were beeing executed fine. But since few weeks they do not seem to run. I checked the /var/adm/cron/log file and I can see the job has been scheduled for the correct time.
CMD: "name for the command and path"
> root 20536 c Tue May 25 16:47:00 WST 2004
< root 20536 c Tue May 25 16:47:00 WST 2004 rc=1

But I can the rc=1 and the job does not get executed.

What should I check for this. Thanks in advance for your help.

Indira A

[Johan Lorimier]

Hi,

using cron you do not have your environnement variables as PATH and so on. You have to specified the path of each command or to include variable definition in your script.

Johan

[Indira Aramandla]

Yes I do specify the complete path and name of the script. I just gave the name and path as command and path.

Eg:- This is how we schedule.

30 01 * * 1 /usr/local/bin/bootable_tape.sh > /usr/local/logs/bootable_tape.log

In order to schedule a ignite tape creation jon wvery monday morning at 01:30 hours.


Indira

[Jeroen Peereboom]

Indira,

rc=1 means that the command that has been executed exited with returncode equal to 1.
This means you must check your script and its logfile to find the error. According to the cron logfile, the job exits almost immediately. Is there a command 'exit 1' in the script? An easy way to see how far the script gets is adding a 'set -xv' command at the beginning. It will show all commands being executed.

Are ALL root's cronjobs failing? Any messages in syslog at that time?

JP.

[Indira Aramandla]

This thread has been closed