Support

Akeeba Backup for Joomla!

#9222 Site paths determined by this script

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 Monday, 12 December 2011 04:30 CST

user47707
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? yes
Have I searched the forum 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: (optional, but it helps us help you)
Akeeba Backup version: 3.3.10

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 use the backup.php script in akeeba, but I get this message on email:

Current memory usage: 140.79 Kb

Unsetting time limit restrictions.

Site paths determined by this script:
JPATH_BASE : /is/htdocs/wp1084xxx_9MHNMG0DNY/domain/administrator
JPATH_COMPONENT_ADMINISTRATOR : /is/htdocs/wp1084xxx_9MHNMG0DNY/domain/administrator/components/com_akeeba

can you help me?

thanks
regards
Otto Kolbe

nicholas
Akeeba Staff
Manager
Hello Otto,

It looks like the script fails loading the actual backup engine to start the backup. Please try the following:
- Download the installation ZIP file of Akeeba Backup Progressional 3.3.10 again from our site (I want to make sure we don't have a broken archive)
- Install it on top of your existing installation
- Retry backing up

If the problem persists, please double check the PHP version you're using. If it's anything lower than 5.2.7 you might end up with trouble.

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!

user47707
Hello,

I got the same message, and the PHP Version is 5.2.17

regards
Otto

nicholas
Akeeba Staff
Manager
Hello Otto,

Please follow exactly the same procedure and tell me what your results are. Thanks!

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!

user47707
Hello,

1. I have install the Akeeba Backup Progressional 3.3.10 on top of the existing Installation.
2. I have start an Backup with the cronjob

3. I got this message:
Current memory usage: 140.79 Kb

Unsetting time limit restrictions.

Site paths determined by this script:
JPATH_BASE : /is/htdocs/wp1084xxx_9MHNMG0DNY/domain/administrator
JPATH_COMPONENT_ADMINISTRATOR : /is/htdocs/wp1084xxx_9MHNMG0DNY/domain/administrator/components/com_akeeba


thanks

regards
Otto

nicholas
Akeeba Staff
Manager
I can't understand why this is happening. I just tried four setups (two local and two live hosts) with PHP 5.2.17. In all cases, a fresh installation of Akeeba Backup Pro 3.3.10 worked, so we don't have a bug affecting PHP 5.2 hosts (trust me, I would have known about it before you, as I do have live sites hosted on servers with PHP 5.2). Now, this leaves us with the question, what happened?

The paths I see over there look correct, so it can't be a failure in locating the backup engine's files. I have confirmed that the backup engine can load on PHP 5.2. It can't be a memory limit issue, as at this point the maximum memory consumption is 3.74 Mb and it never peaks above 8Mb before the first backup step runs (which it hasn't yet). It can't be a timeout issue either, as we're still in the first two seconds of execution. This leaves me with pretty much no explanation as to what is going on :s Can you ask your host if there is a PHP error log for command line scripts? This is the only thing which could shed some light.

There is also a very small possibility of having the wrong PHP version available in the command line, e.g. PHP 5.1, which would explain why this happens. In order to determine that, please create a CRON job whose command is "/path/to/php -v" where /path/to/php is the full path to your PHP binary, as you have set it up in your other CRON job which runs the backup.php file. You should receive an email with something like this:
PHP 5.3.6 with Suhosin-Patch (cli) (built: Sep  8 2011 19:34:00) 
Copyright (c) 1997-2011 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2011 Zend Technologies

Please paste that information here so that I understand which PHP version and binary (cli or cgi) you are using with the backup.php script.

Alternatively, please try using the altbackup.php script. If this fails too, you will have to setup a CRON job with the front-end backup feature, as explained in the first section of our Automating Your Backup documentation chapter.

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!