Support

Akeeba Backup for Joomla!

#16543 Scheduling via CRON Joomla 3 aware yet?

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 Thursday, 27 June 2013 06:09 CDT

Adam_NZ
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: Joomla! 3.0.4 Stable
PHP version: 5.3.21
MySQL version: (unknown)
Host: http://www.warkworthmedicalcentre.co.nz/
Akeeba Backup version: Akeeba Backup Professional 3.7.7

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 run AKB 3.7.7 very successfully on all my Joomla 2.5.4 sites - storing the backups to a central server via FTP. Works like a charm!

However - when attempting to do it on a Joomla 3.0 site, I get all sorts of errors:

require_once(__DIR__/platform.php): failed to open stream: No such file or directory in [deleted] /httpdocs/libraries/import.php on line 29

I compared the various files with their J2.5 equivalents - so I edited that to get around it ... then get:

Fatal error: Class 'JDispatcher' not found in [deleted] /httpdocs/libraries/joomla/event/dispatcher.php on line 72

I try the odd thing but get more/different errors.

Any ideas?

Thanks,

Adam.

nicholas
Akeeba Staff
Manager
Joomla! 3.0 is no longer supported for use with our software. As a result it would come as a big surprise if the CRON script did work on Joomla! 3.0. Please upgrade to Joomla! 3.1 for security reasons above anything else and install the latest dev release of Akeeba Backup which includes a CRON script that works with it.

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!

Adam_NZ
Thanks, Nicholas - speedy response as ever!!

I was relying on the Joomla update emails - which for some reason I wasn't getting for my one Joomla 3.0 site. I didn't realise 3.1 was out! Thanks!

Updated to 3.1.1 no problems, Grabbed and installed AKB svn1967(Alpha) - again no problem.

However ... the CRON script fails with:

Warning: require_once(/includes/defines.php): failed to open stream: No such file or directory in [deleted] /httpdocs/cli/akeeba-backup.php on line 62

Fatal error: require_once(): Failed opening required '/includes/defines.php' (include_path='.:/usr/share/php') in [deleted] /httpdocs/cli/akeeba-backup.php on line 62

Yet defines.php is there.

Regards,

Adam.

Adam_NZ
EDIT: I enabled the FRONT END version (with secret word) and that ran OK.

I re-set the CRON script to fire again. Same error as before.

Adam.

nicholas
Akeeba Staff
Manager
> I was relying on the Joomla update emails - which for some reason I wasn't getting for my one Joomla 3.0 site. I didn't realise 3.1 was out! Thanks!
There was a bug in Joomla! 3.0 and only long term support (LTS) releases would be reported. This means that until 3.5 is out next year it shows no updates. Please rely on the much better Joomla! updater in Admin Tools. Also note that both update methods (core Joomla! and the one in Admin Tools) are written by yours truly but I no longer have control to what happens to Joomla!'s own updater, including the proper settings that need to be set up when a new Joomla! version is shipped.

Regarding the CRON script, it seems that your server is reporting the wrong path to akeeba-backup.php. My educated guess is that the command line PHP version is 5.2 which is too old and doesn't work with our backup script. Can you please verify that with your host, obtain the path to the PHP 5.3 CLI binary and use it in your CRON job please?

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!

Adam_NZ
Hi Nicholas,

Thanks for the info and help.

I'm intrigued that the path to the CLI executable comes out wrong, as the same path works fine on the same server for all your Joomla 2.5 scripts.

Upgrading to a newer version of PHP is (sadly) not an option. It took 1.5 years to persuade the host to "upgrade" to even this ancient version. If you think Cyprus/Greece is bad, you should try New Zealand. IT infrastructure is abysmal - and not much choice.

**ANYWAY** ... the good news is that I tried the "front end" method via CRON. Both the WGET and CURL methods worked fine - so that's good to know!

As ever, thanks for your amazing add-ons and fantastic support,

Adam.

nicholas
Akeeba Staff
Manager
Adam,

PHP 5.2 went end of life on January 2011 and receives no security updates since then. PHP 5.3 entered its end of life notice period this month, June 2013 (it may receive a few security updates for the next coming months, if a major security issue is discovered). If your host is still on an outdated version of PHP –with known and sever security issues– and two end-of-life PHP generations behind, well, maybe it's time to look for another host. Being hosted in the US will only increase the latency by 100msec or less and can get you decent, up-to-date hosting.

The hosting landscape in Greece and Cyprus is equally bad. I am hosted on a US server so as not to be affected by it. Despite the server being halfway through the world and having to follow a very crooked path (diagonally across the US and diagonally across Europe) my site is really fast to reach:
round-trip min/avg/max/stddev = 174.578/176.759/178.106/1.392 ms

Having a speedy, secure, up-to-date host across the globe is significantly more performant and sane than having a slow, insecure, outdated host in your back yard. You don't even know if the servers are actually in your country or halfway across the globe, anyway; some "Greek" hosts actually have their servers in Netherlands or the US due to the exorbitant prices of the very few Greek data centres. This is something you should consider.

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!

Adam_NZ
Nicholas,

Thanks for your help/advice. I may just have to look at the US servers thing again. I got badly bitten by a couple of US companies whose service started out great then deteriorated terribly. I also had a problem with the 12hr time difference (for urgent support calls). Any hoster recommendations?

The difficulty is that NZ's connection to the rest of the world is chronic (one ancient fibre-optic cable to Australia). 90% of my clients are local - and sometimes traffic to anything outside NZ is simply saturated.Many NZ businesses have lobbied the government, but they're either broke, ignorant or simply in denial.

Adam.

Adam_NZ
Aha! Spotted you on a Siteground (Hosting) review!

Adam.

nicholas
Akeeba Staff
Manager
The standard list of hosts I recommend, in no particular order, are: SiteGround (US & EU), CloudAccess.net (US), Rochen (US & EU), iRedHost (EU). If your sites are mostly static content (as opposed to different content per logged in user, which is the case of our site) you may even use a CDN such as CloudFlare or MaxCDN to maximize the speed for NZ visitors.

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!

Adam_NZ
Thanks, Nicholas. I plumped for Siteground in the end. A fraction of the cost of my NZ hosting - and they have servers in the Asia/Pacific area (it that makes any difference).

Let's see what happens!

Adam.

nicholas
Akeeba Staff
Manager
OK, I wasn't aware of their Asia/Pacific servers. Thank you for pointing this out to me. I have many clients in Australia and New Zealand which are in search of quality hosting. I now know which host I will be recommending to them :)

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!