Failed cron job.. any clues why? 1

[MCubitt]

Hi there.

A cron job fails as:

tle : CMD ( . /oracle/tle/edi_env_sh; $EDIH/xlate/bin/tlreqc -p 4200 -u TLECRON -r Xlato -p -e -l -c $EDIH/xlate/outbound_translation ) : Wed Jul 7 18:45:00 2004
Cron Job with pid: 26130 Failed

tle : CMD ( . /oracle/tle/edi_env_sh; $EDIH/bin/cgw -q OKML -r XMIT ) : Wed Jul 7 18:55:00 2004
Cron Job with pid: 63414 Failed

How can I find out the cause, is there a trace file or something?

Thanks

There's no need for sarcastic replies, we've not all been this sad for that long!

 

[KenCunningham]

Try creating your own log with something like redirecting output from the jobs to a file: yourscript > log.txt 2>&1 should do it. HTH.

 

[iribach]

dont forget:
cron has a very restricted environment

 

[MCubitt]

Thanks guys, we're work on it. Ta.

There's no need for sarcastic replies, we've not all been this sad for that long!

 

[KenCunningham]

I take it these jobs complete if run from the command line? If that's the case, iribach has probably hit the nail on the head and you should ensure that any necessary variables (particularly $PATH) are set explicitly in the script or in a wrapper for the script. Good luck.

 

[MCubitt]

Thanks, we are just in the process of testing that theory. The cron jobs were installed by a software supplier. The 1st error has been identified as a typo in the path name (a common mistake!).

Thanks

There's no need for sarcastic replies, we've not all been this sad for that long!

 

[hyy1109]

I followed this great article to debug and found the problem:

http://www.andrew-gray.com/unixfaq/cron.shtml#setup

 

[KenCunningham]

Thanks for that - useful indeed!