Originally posted by gopi
The moral of the story: make certain your env is set explicitly in the script when running from cron or "path" everything.
I agree. 90% of cronjob problems are because the environment is not setup correctly. You must realize that everything that is done during the login process is not done during a cron execution. I like to create a cron job that has the entry "env" which will echo your environment variables. From there you can usually diagnose what's going on...