Post the output of...
And
...where script_in_question.sh is the script that you are talking about...

-C

Hi Custangro,

Thank you for the reply. But i am not able to understand how why i should use cat.

Because using cat i can only view the file.

then how does it helps me so that the crontab scripts runs.

Thanks,
Ajay

The request by custangro is wise, since if we can see the content of the script (unless it is an X-file) we can have a clue of the issue which prevents the execution from crontab. A typical recommendation is to use absolute paths for the commands within the script, because the crontab runs with a very limited environment and the PATH is usually limited to /bin:/usr/bin. Also in a crontab entry you have to follow some rules about special characters: for example the percent sign %, if written in a crontab, has a special meaning and you have to escape it in order to get the expected behaviour.

So if you show us the actual crontab and the content of the script, we can be more helpful.

So I can take a look at the script...also colucix is right; seeing your crontab would be helpful to

-C

Also, have you checked /var/log/cron for messages generated around the time that the script is supposed to run?

Usually when script run from the command line and doesn't from the cron
it's problem with PATH.

But as was already said seeing your script can help.

Thank you everyone for your help

Below is a crontab that is on Linux 64 bit machine and similarly i have scheduled the crontab on solaris machines also. But only the bewlow script doesn't runs on any machine.

Here is the script that is causing problem.
scripts starts from here:-

#!/usr/bin/ksh


echo "##############################################"
echo "###### Starting new reporting ################"
date
rm /gfs/wlv/colfax/d1/local/XXX/hptolemy/test/scripts/logs/logs-Linux-46-colfax/*.xml

perl /gfs/wlv/colfax/d1/local/XXX/hptolemy/test/scripts/asimlog2xml.pl -m 32bit -S wlv -f /gfs/wlv/colfax/d1/local/XXX/hptolemy/test/scripts/logs/logs-Linux-46-colfax/autosim.log -t /hfs/d1/local/XXX/hptolemy/test/autosim/

rsh koa curl "http://etna.wlv.agilent.com/regression/parser/sc_parse_xml.php?_xmlfile=/gfs/wlv/colfax/d1/local/XXX/hptolemy/test/scripts/autosim.xml"

date

scripts ends here

Below is the look of the crontab

# DEV XXX RSTABLE ptolemy
0 11 * * 0,1,2,3,5,6 ksh /hfs/d1/local/XXX/hptolemy/test/scripts/cvs_update_XXX.sh > /hfs/d1/local/XXX/hptolemy/test/scripts/cvs_sync.log 2>&1
0 11 * * 0,1,2,3,5,6 ksh /hfs/d1/local/XXX/hptolemy/test/scripts/rsync_XXX_rstable.sh > /hfs/d1/local/XXX/hptolemy/test/scripts/linux_sync.log 2>&1
0 12 * * 0,1,2,3,5,6 ksh /hfs/d1/local/XXX/hptolemy/test/scripts/start_list_gen_autosim1_cfx > /hfs/d1/local/XXX/hptolemy/test/scripts/list_gen.log 2>&1

0 13 * * 1,2,3,5,6 ksh /hfs/d1/local/XXX/hptolemy/test/scripts/start_regress_test_autosim1_cfx_cl > /hfs/d1/local/XXX/hptolemy/test/scripts/autosim1_log_cfx_cl 2>&1

0 19 * * 0,1,2,3,5,6,6 ksh /hfs/di/local/XXX/hptolemy/test/scripts/start_dsdiff_report_gen_autosim1_cfx_cl_pista

The last script start_dsdiff_report_gen_autosim1_cfx_cl_pista
is causing problem. This is a report generation script. It doesn't runs at the scheduled time.

And sorry but i haven't checked for this question. **Also, have you checked /var/log/cron for messages generated around the time that the script is supposed to run?**

I am not aware of the above question. Please let me know what is the answer.

Regards,
Ajay

Try to put full paths of the commands within the script: /usr/bin/perl in place of perl, /bin/date in place of date and so on. This is a general rule for crontab scripts, since the PATH of cron is limited in respect of the PATH available to the shell.

Moreover, since you did not redirect the standard error and/or the standard output of the last job, try to see if the owner of the crontab received a mail with some clarifying message. By default stderr and stdout are sent by mail, that one you can see using the command mail from a terminal. If something is wrong, you will find some message from the cron daemon there.

Also make sure that RSH is working between hosts...

-C

Hi Custangro,

I have made the changes you have suggested.

And i have scheduled the scripts. I would report whether i have got some results.

Thanks for your valuable answers.

Thanks,
Ajay

Hi Custangro,

I did all the changes you had suggested but yet the script doesn't runs from crontab.

I would make more research why this doesn't runs. And i would let you know the results with a day.

Thank you everyone for giving the suggestions.

Regards,
Ajay

Doesn't it run or does it abort at a very early stage? You can check the file /var/log/cron to see if the cron daemon actually run the script at the scheduled time or if it just ignored it. For example, you should see an entry like this:
Also check the system mail of the owner of the crontab. If the script actually runs, all the generated standard output and standard error is sent to the user by mail (if not redirected to a file).

One thing you can try is using the "debugger"...start your script like this...

the "-x" shows you what it's doing (since it's in a cron, it should email you the output).

-C