Could be the fact that the default PATH in cron is minimal. Always recommended to specify absolute path to all cmds/files used or (better) put the whole thing in a script, call that and source/specify required PATH.
EG start by cd'ing into your dir, then copy PATH definition from your env.

linosaurusroot

03-04-2013 03:28 AM

I'm shocked it took longer than a week to notice this .. stuff that hasn't been tested should be assumed not to work.

colucix

03-04-2013 03:32 AM

The real problem is that % signs need to be escaped, since they have a special meaning in crontab. The % signs in crontab will be changed to newline and everything after the first % sign is interpreted as standard input to the command. Therefore you crontab entry will result in: