[CGI1.07] Why is my scheduled task (CRON job) not running?

If the scheduled task did not run check the following before contacting support.

1) The file permissions for the script are set correctly, 711 or 755.

2) Be sure that you specify the script interpreter path in the scheduled task path, otherwise the server will not be able to interpret your script code:
- for perl /usr/bin/perl
- for php4 /usr/bin/php
- for php5 /usr/bin/php5

For example, if you're using a PHP5 script located in a subdirectory of your webspace's public_html folder, the full scheduled task path would be:
/usr/bin/php5 /home/sites/domainname.com/public_html/cron/

3) If the script being run is adapted from a cgi script be sure to make the necessary changes as the scheduled task is run by the shell statement such as #!/usr/bin/perl which is needed for cgi, and will be interpreted as a comment.


If you're still having problems, use the test function to help diagnose the issue. You could also add some debugging code to your scheduled task script to see how far it gets or see where it fails.
The output code should be emailed to you once the script finishes running, you can specify where this should be emailed to in the scheduled task section in your Hosting cPanel v7.5 control panel.

Was this answer helpful?

 Print this Article

Also Read

[CGI1.06] Accesses to all files result in '500 Internal Server Error' messages

500 Internal Server Error messages on every page are typically an indication of a misconfigured...

[CGI1.02] My CGI/Perl scripts are failing with error 500 (Internal Server Error)

These errors are nearly always related to a coding error within the script, or bad variables...

[CGI1.05] CGI scripts fail with 'exec format error'

A CGI script must begin with a valid 'interpreter line' also called 'shebang'. That must be the...

[CGI1.04] Why does my script produce a 'file permissions error'?

CGI scripts need certain file permissions to be set if they are to work properly. In general CGI...

[CGI1.01] My CGI/ASP/PHP script is giving an error when trying to write to a file.

This applies to Linux hosting accounts only.This is almost certainly down to incorrect...