cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Go to solution

godaddy cron job not working

i have create cron job but it didn't work it didn't send me any email i test the code alone and i receive an email but when i want to receive from cron job nothing receive it 

that is the command usr/local/bin/php -q /home/mhmd2991/public_html/testcron.php

Minutes Hours Day Month Weekday

1              *          *         *            *

How can i solve this problem ?!

9 REPLIES 9
Employee
Employee
Solution

Re: godaddy cron job not working

You might want to call in to the Hosting Department to get some advice on this one. It seems like someone might have to take a good look in order to help you

Highlighted

Cant get cron job to run.

cron job not running 

php -q /home/content/32/9358832/html/debunknow/index.php

 

 

I am not able to get none running. Any ideas?

 

 

Re: godaddy cron job not working

/usr/bin/php -q /home/iotcpanel/public_html/webfly/iot/cron.php

 

not working please help

Cron Deamon sending emails on success

Hi Community,

 

The cron daemon feature continues to work correctly, however it has just started emailing successful execution results (filling my inbox really quickly).

 

This is the cron command.  I have redacted the hostname and uuid with <masked>

 

--2017-03-29 00:15:04-- http://<masked>.org.au/wp-cron.php?<masked>&action=wysija_cron&process=all
Resolving <masked>.org.au... xxx.xxx.xxx.xxx
Connecting to <masked>.org.au|xxx.xxx.xxx.xxx|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `/dev/null'

0K 21.8M=0s

2017-03-29 00:15:06 (21.8 MB/s) - `/dev/null' saved [104]

 

 

Executing the wget command manually and then executing echo $? return 0.  Which means it is working correctly.   

 

The cron daemon manager indicates "We send Cron job error reports to this email address."  

 

Why am I now receiving emails for a successful cron job execution?  I have made no changes and I have just started receiving this noise.  I cannot tell if there is an error now without filters.

 

Tate

 

 

Re: godaddy cron job not working

/web/cgi-bin/php5 "$HOME/html/path/to/your/script.php"

Re: godaddy cron job not working

/usr/bin/php -f /home/[USERNAME]/[PATH]/script.php

New

Cron jobs stopped working

I had cron jobs in my Linux hosting set up by someone else that were working fine and have now stopped for some reason without any changes being made. I have no ide what might have happened, any ideas?

Re: Cron jobs stopped working

Hi Matt13 - Yes, I had the same thing happen today.  Cron was successfully running 3 days ago and then abruptly stopped. I called GoDaddy support, and while on the phone everything mysteriously started working once more without any reason as to why this occurred.

Alvin Brown
Digital Strategist

Re: Cron Deamon sending emails on success

 bluedogtech : Try exit 0; instead of return 0;

 

I have had zero luck in getting the Cron Job Manager to successfully install a crontab.  I can see the crontab using /usr/bin/crontab -l.  However, it fails to execute, because of the quotes on the MAILTO= statement.  You cannot prevent the Cron Job Manager from doing this.  Even removing the email address it will use MAILTO=""  This causes the failure to execute the crontab.

 

You can use an ssh shell and use /usr/bin/crontab <path to crontab> to successfully install a crontab. When using MAILTO=, DO NOT use quotes around the email address you provide.  Also, if you use $HOME in the script path, define your absolute home path using HOME=<path> again no quotes.

 

for example the file mycrontab contains

# canary

SHELL=/bin/sh

MAILTO=your@emailaddress.com

HOME=<your absolute path to home>

00 * * * * "$HOME/html/private_data/test.sh"

15 * * * * /web/cgi-bin/php5 "$HOME/html/private_data/testcron.php"

 

to install mycrontab use /usr/bin/crontab <path>/mycrontab

 

once installed, you can check it by using /usr/bin/crontab -l 

and edit it by using /usr/bin/crontab -e

and remove it by using /usr/bin/crontab -r

 

good luck