Support

Akeeba Backup for Joomla!

#8858 CRON backup not working - error in shell - works on other domains.

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 nicholas on Tuesday, 24 May 2011 02:37 CDT

davesage
Mandatory information about my setup:

Have I searched the forum before posting? Yes
Have I read the Troubleshooting Wizard before posting? Yes
Have I read the documentation before posting? Yes
removed after support given

EXTREMELY IMPORTANT: Please attach your Akeeba Backup log file in order for us to help you with any backup or restoration issue.

Description of my issue:

I am trying to setup CRON to automate backups. I've done it on two of my domains perfectly fine but I got to the next one and it won't work. All domains are setup the same with the same versions and on the same servers etc..

When I run the script in a shell it comes back with an error 'This script could not detect your live siteis URL. Please visit Akeeba Backup's Control Panel page...'

I've obviously been to the control panel to setup the backup profile for the CRON job (which I've run manually and it works ok) I've set all the normal 'front end access' and 'secret word' stuff etc..

It all works fine on the other two domains I just can't work out why it won't work on this one - which to my knowledge is the same setup.

Could it be length of the domain name or ATPRO settings or something?

Cheers,

Dave

nicholas
Akeeba Staff
Manager
Ah, this error pops up from time to time but I can't trace it down to something specific. I will ask you to do a seemingly pointless procedure that actually helps (as in: it does work!).

- Go to Akeeba Backup and click on Component Configuration. Don't change anything, just press Save.
- Log out of your site and log back in.
- Go to Akeeba Backup's Control Page.
- Go to the Configuration page and click on Save.
- Repeat the above step once more.

Now the live site URL should be saved to a hidden component configuration option and the CRON job should be able to work again.

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!

davesage
Thanks for the quick response. I've tried this and I'm still getting the same error.

I might be confused though:

Your first bullet mentions 'Component Configuration' is this the same as the control panel configuration you mention in bullet 3-4? I'm not sure I can see another place where it is 'Component configuraiton' sorry.

Cheers,

Dave

davesage
interstingly I was using altbackup.php (not sure why) if Itry backup.php it seems to work ok.

Think I'll just use backup.php instead!

Cheers,

Dave

PS - interesting that the backup file produced in this way has a name of '...-unknown_host-...jps'. Seems as though it still doesn't know the domain but it doesn;t stop it from working when using backup.php as apposed to altbackup.php?

nicholas
Akeeba Staff
Manager
I am working on a permanent solution for that, to be included in the next release.

Regarding the difference between backup.php and altbackup.php, it's by design. backup.php runs the backup entirely from the command line. It doesn't run Joomla! at all. Everything is handled by Akeeba Engine, our backup framework. The name shows unknown_host as it can not load the (missing) live site URL from the component configuration.

On the other hand, altbackup.php works pretty much as the standard front-end backup. It calls the front-end backup URL of your site. In order to do that, it requires that the live site URL is stored in the component's configuration. If it's not, it can't figure out which URL it should call and simply fails.

I am wondering, are you using any kind of caching in your site's Global Configuration? If so, what is the cache time and what is the cache engine you're using (e.g. 15 minutes, files)?

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!

davesage
Cache is off

nicholas
Akeeba Staff
Manager
OK, I found out the problem. It was caching, all right, but not what I thought. Joomla! was caching the component parameters, so having both Live Update and the magic autosave of the site's URL run back-to-back caused one of them to be always discarded. I fixed that and you can use the latest dev release which fixes this issue. Thank you in advance for your feedback!

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!

davesage
Hi,

Didn't spot this last update till now!

You are a star! Thanks for looking into this.

Dave

davesage
The link doesn't work :-(

But the error page is cool :-)

davesage
Picked up SVN-590 from the top menu! Thanks!

nicholas
Akeeba Staff
Manager
FYI, I just published yet another developer's release which adds some interesting superpowers to the component, like taking an automatic backup of a single extension upon upgrading it through the Joomla! extensions installer ;)

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!

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!