CRON job not working
By Eden Clemente on Thursday, 10 October 2013
Posted in Technical Issues
Replies 1
Likes 0
Views 2.3K
Votes 0
Hi, I have set up a cron Job onto my server but it doesn't work.

I tested the script but the result was showing nothing, then I assigned my email for the output and saw that the access is denied.
I am going to post here the conversation with the Hosting Company Support Desk:

Hi, I tried to run this cron job onto my website but the connection gets refused:
/usr/bin/wget -O /dev/null "http://www.fx2.it/index.php?option=com_easyblog&task=cron";

I don't know if the path is correct and the permissions are ok as I don't think I have access to those
areas of the server. This is the error message:

--2013-10-10 01:05:03-- http://www.fx2.it/index.php?option=com_easyblog&task=cron Resolving
http://www.fx2.it... 79.170.44.102 Connecting to http://www.fx2.it|79.170.44.102|:80... failed: Connection refused.
---------------------------
Hi Eden,

Thank you for contacting us.

Opening that via HTTP will be disallowed because we block 'loop-back' requests. Try instead with the full server path ->

/home/sites/fx2.it/public_html/index.php?option=com_easyblog&task=cron
-----------------------------

so would the entire script be:
/usr/bin/wget -O /dev/null "home/sites/fx2.it/public_html/index.php?option=com_easyblog&task=cron" ?
-----------------------------
Hi Eden,

Thank you for your reply.

That may be because the script has no direct output redirected? What if you run it directly in your browser?
Hello Eden,

So sorry for the delay in getting back to you. Please find the replies as below.

- The fact that .ZIP files are among the file types accepted but only images can be sent via email is a pity... it means that all the other file formats have to uploaded from the back-end... not practical.
>> Unfortunately for now this is unsupported I will add this in the request list to be reviewed by the team.

- The Cron Job is still not timed very well but I am trying to set the CRON Job to 3 minutes and the Easyblog Settings to 5 minutes to see if this way the software is happy.
>> This is a good approach. I hope it solves your issue.

- I had written the result of the CRON Job that was emailed to me by the server to ask why the script is reporting errors despite it "works" (at present apparently I can send an email and most of the times it arrives and gets processed), this is at present not been answered by the Support Team. At least they should acknowledge that the script works but there seem to be errors...
>> I have replied to you about this but I seem to have misunderstand you. The errors for the parse_url is not coming from EasyDiscuss. In fact if there is any error from EasyDiscuss you would see it after the "Content-type: text/html"

- Apparently it seems also that despite having a 64MB limit set by PHP, if in the maximum file size allowed in the back-end settings I change the value to "0" (Unlimited), the system refuses completely any file of any size. I couldn't even upload them via back-end whilst writing the blog, I had to change the value to something different from 0...
>> I have tested this and yes this seems like a bug in EasyDiscuss. I have at present added this to our task list so that we can fix this for the next release of EasyDiscuss.

Thanks!
Adelene
·
Wednesday, 30 October 2013 01:24
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post