Timeline for Cron job not executing
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 11, 2011 at 21:55 | comment | added | laebshade |
How about the shebang? Does the first line say: #!/bin/sh or #!/bin/bash -- this may be your problem.
|
|
| Sep 6, 2011 at 10:07 | comment | added | Eric Wilson |
@Giles But my script was executable. I had executed it from the command line, and confirmed that all three xs were there.
|
|
| Sep 6, 2011 at 7:22 | comment | added | Gilles 'SO- stop being evil' |
@EricWilson Cron executes the command through a shell. With a non-executable myscript.sh isn't executable, that shell emits the error message /etc/mycron/myscript.sh: Permission denied and moves on to the next instruction (i.e. exits, since this is the only instruction). The error message is sent through local e-mail to your account, like all output from a cron job. If you haven't installed an MTA, the cron job output is lost.
|
|
| Sep 6, 2011 at 2:10 | comment | added | Eric Wilson |
OK, adding sh made it work. What was cron trying to do when it wasn't there? I'd really appreciate some insight here, otherwise I'll superstitiously add sh to cron jobs indefinitely.
|
|
| Sep 6, 2011 at 2:08 | vote | accept | Eric Wilson | ||
| Sep 6, 2011 at 2:02 | comment | added | Eric Wilson |
It is executable, thanks for asking. (Really) I'm curious what difference adding sh makes. (I'm trying it, I just don't have any idea what it could mean if it works.)
|
|
| Sep 6, 2011 at 1:53 | history | answered | laebshade | CC BY-SA 3.0 |