Cronjob

[Scott D. Allen]

I've got a cronjob that runs fine from the command line as root, but doesn't run in the cron. Actually, it runs, but it dumps out before executing correctly and doesn't produce any errors.

30 * * * * /opt/scripts/script > /var/tmp/script.log 2>&1

It produces a log file inside the script, which gets created every half hour, but it's empty and so is the log file.

--Scott

[Andreas Voss]

Hi,

don't know what script you have.
If it's a bourne/korn (sh/ksh) script
insert at the top a line like:
set -x
this generates a trace to stdout.
Perhaps you can look in the mail for these
messages.

Regards

Andrew

[Brian M. Fisher]

My guess is there are environmental variables that are not getting set when the job is run via cron. Make sure to set all required variables within the script.

If you do not want a new log file created at each execution use >> instead of >.

Brian
<*(((>< er

[Scott D. Allen]

Thanks guys. I was using the wrong syntax in one of my commands and it was doing an exit 0.

--Scott

[Chris Ermlich]

Scott,

Not knowing what your script does, you might want to check if any directories or commands are being used in the script that have to have 'root' access (since it's running fine from the command line when executed as 'root'). Is the cron job running as 'root' or as user 'xyz'?

Chris :-)