Support

Akeeba Backup for Joomla!

#11025 Undefined variable: archiver

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 Friday, 10 February 2012 11:12 CST

user51333
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?)? Akeeba
Joomla! version: 1.5.25
PHP version: 5.2.17
MySQL version: 5.0.92
Host: WiredTree
Akeeba Backup version: AkeebaPro 3.3.13

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'm trying to do a SQL only backup of 4 different databases (the main Joomla one, + 3 others).

The process of backing up all 4 seems to finish. The finalization process, and upload to Amazon S3 fails with a 500 error. The log shows the following culprit:
DEBUG |120209 11:03:30|PHP NOTICE on line 190 in file /administrator/components/com_akeeba/akeeba/core/domain/db.php:
DEBUG |120209 11:03:30|Undefined variable: archiver

The backup process works fine for another configuration I have which also backs up the files from all 4 sites.

Thanks,
Alex

user51333
Not sure if my log attached the first time..

nicholas
Akeeba Staff
Manager
Nice catch! This is mostly a cosmetic bug, but I'll fix it on the next release anyway :)

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!

user51333
I don't think it's just cosmetic though. I get a 500 server error through the admin area (in the iFrame) and the file does not properly upload to Amazon (though the files are on my server).

I just ran through the cron command line, and the last few lines of the log are:

DEBUG |120209 12:06:43|AECoreDomainDb :: No more databases left to iterate
DEBUG |120209 12:06:43|----- Finished operation 247 ------
INFO |120209 12:06:43|Finalizing database dump archive
DEBUG |120209 12:06:43|PHP NOTICE on line 190 in file /administrator/components/com_akeeba/akeeba/core/domain/db.php:
DEBUG |120209 12:06:43|Undefined variable: archiver
DEBUG |120209 12:06:43|
--- END OF RAW LOG ---

Where it abruptly ends. Looking at line 190 of that file, the $archiver is set in an if statement above. It seems it's not being set due to some configuration settings I have, which is then causing the execution to halt when $archiver is trying to be used on 190.

Thanks for looking into this,
Alex

nicholas
Akeeba Staff
Manager
Hi Alex,

Most likely you are right. In this case, please follow these instructions to disable multipart uploads and immediately upload parts options.

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!

user51333
I was incorrect. The files are not saved on my server, so the jpa archive doesn't ever seem to be finished/saved to disk even before the attempt to upload to Amazon.

The error in the iFrame after backup is:
The backup operation has been halted because an error was detected.

The last error message was:



AJAX Loading Error

HTTP Status: 500 (Internal Server Error)

Internal status: error

XHR ReadyState: 4

Raw server response:


I just set post-processing to "Disabled" to remove Amazon from the equation altogether and get the same issue. Attached is the most recent backup log with S3 upload disabled.

Thanks,
Alex

nicholas
Akeeba Staff
Manager
Hello Alex,

Can you please install the latest developer's release of Akeeba Backup Professional, svn1231, and retry taking a backup? If it still fails, please post the new backup log file. 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!

user51333
Installed. It now starts backing up some of the tables and I can see some progress. Then I get a 500 error with:
-----
The backup operation has been halted because an error was detected.
The last error message was:

Can't modify configuration after the preparation of
Please click the 'View Log' button on the toolbar to view the Akeeba Backup log file for further information.
-----
I think the first ('this' Joomla installation) gets backed up. It's when moving to the next database that problems happen.

New log from the SVN release attached.

Thanks for your support,
Alex

nicholas
Akeeba Staff
Manager
Hi Alex,

You are right, the multiple database backup feature did not work. I fixed that in the latest dev release, svn1232. Can you please download and retry the backup?

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!

user51333
svn1232 did the trick. The backups with multiple database only (no files) now is working and is also going to Amazon S3 as expected.

Thanks for the great help,
Alex

nicholas
Akeeba Staff
Manager
Perfect! Thank you 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!

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!