Support

Akeeba Backup for Joomla!

#12815 cron for cloudaccess.net url field

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by on Thursday, 09 August 2012 18:00 CDT

user6466
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? yes
Have I searched the tickets before posting? yes
Have I read the documentation before posting (which pages?)? yes
Joomla! version: 1.5.25
PHP version: (unknown)
MySQL version: (unknown)
Host: cloudaccess.net
Akeeba Backup version: pro

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue: I attached a screencap of their field.

I moved the site from Hostgator to cloudaccess as one of the sites you recommended, thank you so far they have been excellent.

Having a isssue with figuring out what to actually write in the url field of the cron job to get it to do the backup post processing to dropbox.

I tried all paths and put the syntax in you state in your documents but to no avail

I get error below in the return email

Result of cron job
Getting administrator/components/com_akeeba/altbackup.php
--------------------------------------------------------------------------------
[Errno 2] No such file or directory: 'administrator/components/com_akeeba/altbackup.php'


I have tried all levels of this path below with same result errors
/mnt/data/vhosts/bladdercancersupport.org/httpdocs/administrator/components/com_akeeba/altbackup.php

The altbackup.php file does exist in that folder. Is their info before this path I need to add?


I believe I need the correct root path (where /usr/local/bin/php is the path to your PHP CLI executable and /home/USER/webroot is the absolute path to your web site's root) or the syntax I am using for the url field is incorrect.




nicholas
Akeeba Staff
Manager
CloudAccess.net tries to access a URL in their CRON job. It doesn't try to run a script. What you try won't work because it expects a URL and you are giving it a filesystem path. These are apples and oranges; if you mix them you get a fruit salad at best. That said, even if you use the correct front-end backup URL I don't think it will work. You have two choices:
1. Ask CloudAccess.net about the proper way to set up a CLI script to run as a CRON job.
2. Use the third party webcron.org service as described in our documentation.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user6466
Thanks Nicholas , yes I knew that one is a script executable and the other cloudaccess is looking for is an Url. I thought perhaps cloudaccess was either not being totally accurate with their field title or there was an url that we could use like you suggested "correct front-end backup URL".

Cloudacccess cron form is certainly not allowing PHP CLI executable commands of any kind so it is limited.

Okay thanks I will have to look at an external trigger like webcron.




nicholas
Akeeba Staff
Manager
You're welcome!

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user6466
We have had limited and intermittent success.

This is the line Cloudaccess put in the Url field

http://bladdercancersupport.org/index.php?option=com_akeeba&view=backup&key=test

This is what we were first getting in the Email response:
Result of cron job
Getting http://bladdercancersupport.org/index.php?option=com_akeeba&view=backup&key=test
--------------------------------------------------------------------------------
('http protocol error', 0, 'got a bad status line', None)

The last two days we are getting this:
Result of cron job
Getting http://bladdercancersupport.org/index.php?option=com_akeeba&view=backup&key=test

So now without the error reported.

The problem is in Dropbox we have received the correct .jpa files once or twice the other times we have not received anything and on one occasion only one of the 10 .jpa files. I split them at 10mb on Christopher's request.

On another event it stated it was successful in Joomla but it did not send the files to dropbox it sent them to the akeeba backup folder.

And today it did not send anything.

I attached the frontend log from Akeeba







user6466
Well I tried to attach the log file

But I was not able to with this error reporting

JFile: :read: Unable to open file:
Warning: Failed to move file!
You are not authorised to view this resource.

nicholas
Akeeba Staff
Manager
It looks like CloudAccess.net's CRON facility doesn't allow accessing URLs which use redirects, like Akeeba Backup's front-end backup URL. As I wrote above, you have another (very well tested) alternative: using webcron.org.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user6466

Christopher from Cloudaccess asked me to forward you theses questions below to try to rectify the dropbox automated cron job.

"if this is the same problem with SSL Cert. Seems to me that SSL is not be passed when communicating with dropbox. Ask him if the same patch from his other product will work here.


Have you asked Nicolas, about the SSL issue that he found with another one of his issues. He has found that on some hosting servers when connecting to outside sources there is a problem. he found that the server cert.pem is not be used when making a curl request to a S3. This might be the same issue you are seeing here. WHen ran Manually, the Cert is being pasted, When cron runs it, most of the time cert.pem is not being passed. "

nicholas
Akeeba Staff
Manager
Akeeba Backup 3.4.x and 3.5.x does use its own copy of cacert.pem. But that's completely irrelevant to this issue! We're not talking about my code accessing a URL, we are talking about CloudAccess' CRON facility not supporting following HTTP 302 redirects. What does the SSL certificate authority cache has to do with that?!

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user6466
Thanks for your patience on this Nicholas. I will forward your response.
I am certainly no expert in how these programs are calling and responding to each other but your explanation clarifies it for me even more.

nicholas
Akeeba Staff
Manager
Please let me know of their reply. I guess the CloudAccess.net guys got confused with a different issue regarding Amazon S3 transfers we had solved a while ago :)

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!