Support

Akeeba Backup for Joomla!

#8375 Backup failed with invalid AJAX data

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, 16 March 2010 05:59 CDT

Monday, 15 March 2010 09:40 CDT

tabletguy
Unable to attach a log file. I can upload one, but the Green Check Circle doesn't work. The Red Minus DOES work, and drops the upload. Nothing will return to the "New Topic" composition page.
--------
However, the log file does not show any errors. Emailing it to Nickolas anyway.
Stephan
------------------
Backup Failed
The backup operation has been halted because an error was detected.
The last error message was:
Invalid AJAX data:
Fatal error: Call to a member function getState() on a non-object in T:\xampp\htdocs\bindu\administrator\components\com_akeeba\akeeba\core\kettenrad.php on line 157
Please click the 'View Log' button on the toolbar to view the Akeeba Backup log file for further information.
Before posting to the support forum for assistance please read the User Guide first!.

Monday, 15 March 2010 09:45 CDT

tabletguy
What might not be obvious from the log file is that I was running under a local copy of XXAMP, Windows Vista 32 bit, 4 gb memory. I've pasted the first 100 lines or so from the log here anyways.
========
INFO |100315 20:17:44|--------------------------------------------------------------------------------
INFO |100315 20:17:44|Akeeba Backup 3.0.a3 (2010-03-12)
INFO |100315 20:17:44|Got backup?
INFO |100315 20:17:44|--------------------------------------------------------------------------------
INFO |100315 20:17:44|--- System Information ---
INFO |100315 20:17:44|PHP Version :5.2.9
INFO |100315 20:17:44|OS Version :Windows NT
INFO |100315 20:17:44|DB Version :5.1.33-community
INFO |100315 20:17:44|Web Server :Apache/2.2.11 (Win32) DAV/2 mod_ssl/2.2.11 OpenSSL/0.9.8i mod_autoindex_color PHP/5.2.9
INFO |100315 20:17:44|PHP Interface :apache2handler
INFO |100315 20:17:44| version :
INFO |100315 20:17:44|Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.8) Gecko/20100202 Firefox/3.5.8 (.NET CLR 3.5.30729)
INFO |100315 20:17:44|Safe mode :
INFO |100315 20:17:44|Display errors :1
INFO |100315 20:17:44|Error reporting :E_ERROR | E_WARNING | E_PARSE | E_CORE_ERROR | E_CORE_WARNING | E_COMPILE_ERROR | E_COMPILE_WARNING | E_USER_ERROR | E_USER_WARNING | E_USER_NOTICE
INFO |100315 20:17:44|Disabled functions :
INFO |100315 20:17:44|open_basedir restr.:
INFO |100315 20:17:44|Max. exec. time :360
INFO |100315 20:17:44|Memory limit :128M
INFO |100315 20:17:44|Current mem. usage :5991496
INFO |100315 20:17:44|GZIP Compression : available (good)
INFO |100315 20:17:44|JPATH_BASE :\administrator
INFO |100315 20:17:44|JPATH_SITE :
INFO |100315 20:17:44|JPATH_ROOT :
INFO |100315 20:17:44|JPATH_CACHE :\administrator\cache
INFO |100315 20:17:44|Computed root :
INFO |100315 20:17:44|Output directory :\administrator\components\com_akeeba\backup
INFO |100315 20:17:44|Temporary directory:/tmp
INFO |100315 20:17:44|--------------------------------------------------------------------------------
INFO |100315 20:17:44|Akeeba Backup has detected the following potential problems:
INFO |100315 20:17:44|- 203 Default output directory in use (medium)
INFO |100315 20:17:44|You probably do not have to worry about them, but you should be aware of them.
INFO |100315 20:17:44|--------------------------------------------------------------------------------
INFO |100315 20:17:44|Loaded profile #1
DEBUG |100315 20:17:44|----- Finished operation 1 ------
DEBUG |100315 20:17:44|Archive template name: site-[HOST]-[DATE]-[TIME]
DEBUG |100315 20:17:44|Expanded template name: site-localhost-20100315-131744
DEBUG |100315 20:17:44|Backup type is now set to 'full'
DEBUG |100315 20:17:44|Expanded archive file name: /administrator/components/com_akeeba/backup/site-localhost-20100315-131744.jpa
DEBUG |100315 20:17:44|Initializing archiver engine
DEBUG |100315 20:17:44|AkeebaPackerJPA :: new instance - archive /administrator/components/com_akeeba/backup/site-localhost-20100315-131744.jpa
DEBUG |100315 20:17:44|AkeebaPackerJPA :: Killing old archive
DEBUG |100315 20:17:44|----- Finished operation 2 ------
DEBUG |100315 20:17:44|----- Finished operation 3 ------
DEBUG |100315 20:17:44|Successful Smart algorithm on AECoreDomainInit
DEBUG |100315 20:17:44|Kettenrad :: Domain 'init' has finished.
DEBUG |100315 20:17:44|====== Finished Step number ======
DEBUG |100315 20:17:44|Sleeping for 1714.57099915 msec, using usleep()
DEBUG |100315 20:17:46|Saving Kettenrad instance
DEBUG |100315 20:17:51| -- Loaded stored Akeeba Factory
=======================

Monday, 15 March 2010 21:34 CDT

nicholas
Let's try something simple first. First, upgrade to 3.0.a4 as the version you are currently using suffers from a major bug which affects the database backup (some tables will be skipped from the backup set). Then, just go to Configuration and click on Save - once for each backup profile you may have created. The bug which made this necessary is also fixed in 3.0.a4, so future upgrades shouldn't require you to go through this chore.

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!

Monday, 15 March 2010 23:43 CDT

tabletguy
Sorry I hadn't noticed an updated version. Does the software automatically report new versions and do in place upgrades, like the older one?

Anyway, the backup did work this time. Again, it's not production, and it's on a local portable hard drive (testing), so it wasn't critical.

I hope all the issues from the backup failure were caught with this release . (Such as failing, but no failure message in the log file, manage files showing obsolete instead of failed, etc.

Tuesday, 16 March 2010 00:32 CDT

nicholas
The auto updater is not in place yet because I have to add update notifications support to the site first. If you peek around the code you'll see that it's there, but commented out. I am working on this.

I think all issues are caught, but if you run into a problem, please report it. It's impossible to test software on all possible server configurations; maybe I missed something. Just report a bug and I'll squash it in a matter of minutes, like I always do :D

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!

Tuesday, 16 March 2010 04:01 CDT

tabletguy
Well, one thing that annoyed me a bit (I didn't read documentation first) was that I installed it, and expected it to magically replace the existing JoomlaPack, which it didn't. It installed separately.

That's actually OK, and I thought it was kinda cool, actually. But, then I discovered that installing AkeebaBackup broke the JoomlaPack backup. So, they don't coexist, apparently.

Also, installing AkeebaBackup didn't copy over the settings from JoomlaPack.

Small annoyances, of course.

Tuesday, 16 March 2010 05:39 CDT

nicholas
Normally both components can happily co-exist, as they don't share settings. However, they also do not know anything about each other's backup output directory settings! This means that for either component to work, you have to use it's directory exclusion filter to exclude the other component's backup output directory. Or assign the same backup output directory for both components. If you didn't do that, JoomlaPack will try to backup the backup files of Akeeba Backup. This will cause a timeout error. Conversely, Akeeba Backup will try to backup JoomlaPack's backup archives but, thanks to its more powerful and smart engine, it will not time out. It will simply produce a bloated backup archive.

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!

Tuesday, 16 March 2010 05:48 CDT

tabletguy
What I meant was that as soon as I installed Akeeba Backup, I tried JoomlaPack (since I noticed it first, and thought perhaps you had installed into the same menu spot.

It immediately gave me a big red error message. Sorry now that I didn't write it down, etc. I didn't realize the two are supposed to coexist. I just assumed the installation of Akeeba caused the other backup to fail, but perhaps I am wrong.

Tuesday, 16 March 2010 05:59 CDT

nicholas
I have them installed on my test servers side-by-side :)

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!