Cron job every day at 9:27 - cron

Question

I'm having some problem with crontab.
I have this job:
27 09 * * * drush #ildeposito.prod status
I want to execute the cron job every day at 9:27.
But it doesn't work.
If I try to execute the command directly in prompt it works.
What's wrong on my crontab?
If I execute "date" from shell I obtain:
mar 3 set 2013, 12.55.13, CEST
If I put the output of date in a file, with a cron job, I obtain:
Tue Sep 3 12:55:01 CEST 2013
Another: this is NOT executed every minute on 13!
* 13 * * * date >>/tmp/temp_out_hour
This works:
*/15 * * * * drush #site.prod cache-warmer --timeout=6 --hub-pages-file=/home/sergej/websites/sute/site-cache.txt
http://www.site.org
The system seems to have problems with hours.

Answer 1

First things first, you need to specify what "it doesn't work" actually means. Do you mean you see no output? Get no mail sent to you with the output? Typically, standard output from cron jobs will be packaged up in an email and sent to the user running the job. If you want to see what the job is outputting, you can use something like:
27 9 * * * drush #ildeposito.prod status >/tmp/temp_out 2>&1
which will write standard output an error to that file (you also don't need the leading 0 in 09).
If a command works from a shell prompt and not from cron, it's usually a difference in your environment settings. You can test this by replacing your job with a very simple one:
27 9 * * * date >>/tmp/temp_out
and examining that file after it executes. If the date works but drush doesn't, your problem lies outside of cron itself.
cron starts processes with a minimal set of environment variables and you have to ensure you've configured a suitable set. See, for example, here:
We use /usr/bin/env to run drush so that we can set up some necessary environment variables that drush needs to execute. By default, cron will run each command with an empty PATH, which would not work well with drush.
When running drush in a terminal, the number of columns will be automatically deteremined by drush by way of the tput command, which queries the active terminal to determine what the width of the screen is. When running drush from cron, there will not be any terminal set, and the call to tput will produce an error message. Spurrious error messages are undesirable, as cron is often configured to send email whenever any output is produced, so it is important to make an effort to insure that successful runs of cron complete with no output.
In some cases, drush is smart enough to recognize that there is no terminal -- if the terminal value is empty or "dumb", for example. However, there are some "non-terminal" values that drush does not recognize, such as "unknown." If you manually set COLUMNS, then drush will repect your setting and will not attempt to call tput.
Other than that, there are numerous other problems that can plague cron:
having a command on the final line of the file with no newline at the end sometimes causes troubles.
having % in your command somewhere.
having had the cron daemon start with a different timezone setting.
That last one can sometimes be fixed just by restarting the daemon. Given your comments about the bizarre nature of the non-performance, I'd suggest that as a first step.