Support

Site Restoration

#14181 com_installer 500 error after restoration

Posted in ‘Site restoration’
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

PHP version
n/a
CMS Type
Other
CMS Version
n/a
Backup Tool Version
n/a
Kickstart version
n/a

Latest post by nicholas on Tuesday, 27 November 2012 12:22 CST

david.joly

LOW PRIORITY problem (we have a workaround).

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: 2.5.8
PHP version: 5.3.13
MySQL version: 5.1.65-cll
Host: Rochen
Akeeba Backup version which took the backup: 3.6.9
Kickstart version used to extract the backup: (unknown)

Description of my issue:

After having copied all the files to restore from a DEV server to a production server, I was not able to get access to com_installer due to an error 500 page. We were able to identify the error in the error_log as

[23-Nov-2012 00:34:19 UTC] PHP Fatal error:  Class 'AEPlatformJoomlacli' not found in /home/action/public_html/administrator/components/com_akeeba/akeeba/platform/platform.php on line 106

When I manually removed the folder /administrator/com_akeeba from the production server com_installer worked flawlessly.

The files were copied several times and from at least 3 different backup files with the same results.

Files were overwritten and it was our first backup restore from version 3.6.9.

We have the same configuration running our DEV with Rochen on the same server without any issues but the Akeeba Backup was installed on DEV server has opposed to copied from the backup on the production server.

We have not reinstalled Akeeba on the production server as of now in case you wanted to investigate further.

If you believe that this might have only been a «perfect storm» of events we will simply update Akeeba on our production server and this ticket could be closed.

 

Thank you,

 

nicholas
Akeeba Staff
Manager

Your live server had a very very old version of Akeeba Backup installed. By restoring a site with a newer version of Akeeba Backup ontop of it you broke Akeeba Backup's installation. You will now have to follow the scenic route to fix this issue. Remove the following folders (some folders may not exist, that's normal):
- administrator/components/com_akeeba EXCEPT the administrator/components/com_akeeba/backup directory and the administrator/components/com_akeeba/akeeba/serverkey.php file. If you remove that directory and that file you will lose your existing backups and/or settings.
- components/com_akeeba
- administrator/modules/mod_akadmin
- media/com_akeeba
- plugins/system/plg_srp
- plugins/system/plg_akeebaupdatecheck
- plugins/system/plg_aklazy
- plugins/system/plg_oneclickaction
Now you can re-install Akeeba Backup.

IMPORTANT: Restoring a backup DOES NOT remove existing files or folders from your server. This can have a detrimental impact on Joomla! itself as wel as its extensions, with leftover files actually causing grave issues to your site. As a rule of thumb you have to remove all files and folders, except user generated content, prior to restoring from the dev to the live server.

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!