Support

Akeeba Backup for Joomla!

#9112 Restore Error 500 Akeeba Pro

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, 01 November 2011 16:41 CDT

user48312

Joomla! version: 1.7.2
PHP version: 5.2.17
Host: 1and1
Akeeba Backup version: Akeeba Backup Professional 3.3.4 (2011-09-12)


Description of my issue: I have an error 500 when i try restore

nicholas
Akeeba Staff
Manager
The 500 error simply tells me that an error occurred. Since you give me no further information, I have no idea if this occurred when Kickstart was extracting the archive, when you were restoring the database contents or during some other step. So, I will have to point you to the troubleshooting instructions.

If it is happening when trying to run Kickstart and before you see Kickstart's page, please take a look at https://www.akeebabackup.com/documentation/troubleshooter/kswontrunatall.html and https://www.akeebabackup.com/documentation/troubleshooter/ksphperrors.html

If the problem happens during the extraction of the backup archive, please take a look at https://www.akeebabackup.com/documentation/troubleshooter/kscantextract.html

If the problem happens after you extracted the archive, as soon as you click on the "Run the Installer" button and before you see any page of the Akeeba Backup Installer, please take a look at https://www.akeebabackup.com/documentation/troubleshooter/abiphperrors.html

If the problem happens during the database restoration, please take a look at https://www.akeebabackup.com/documentation/troubleshooter/abidatabase.html

If the problem happens after you have completed restoring the database, please take a look at https://www.akeebabackup.com/documentation/troubleshooter/abiafterdb.html

In any other case, please try to give me as much information as possible regarding what you did, when the error message occurred and any other information printed out on your browser.

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!

user49333
Hello...

I am trying to copy/restore my live site (hosted by cloudaccess.net) to my local machine (running Xampp). After I run kickstart, I can not accress the front end of my site running on the localhost. I can however access the back end.

I have gone through the article https://www.akeebabackup.com/documentation/troubleshooter/prbasicts.html and verified most of these setting and still have no luck getting the frontend of my site to load. Can you please help? What is going wrong?

user49333
The Kickstart runs with no problem. I run the restoration and cleanup with no problem. Then I am given the option to visit the front end or the back end of my localhost site. This is where the front end does on load.

If I click the link it loads http://localhost/joomla/index.php and I get a 404 error.

If I load the page http://localhost/joomla/ it loads and lists the index of /Joomla

Note: Joomla is the name of the directory for my local test site.

What more information can I give you to help resolve this issue?

rkendallc
@DaBuds - First, please start a new topic whenever you ask for assistance. With so much support happening, we cannot review old topics that are potentially resolved to look for new requests for assistance. This could easily get lost and we dont' want that to happen.

To try and help with your question, Here is a reply to a previous post about 404 errors:

From Nicholas:

Following the QSG's troubleshooting instructions, please take a look at the following:
1. Check your configuration.php for $live_site. If it is not empty, change it to reflect the new domain name, i.e. http://brightstaraviation.com/sandbox.
2. Check you .htaccess files. Try renaming it to htaccess.bak. If your site loads but SEF URLs don't, edit your htaccess.bak file, try removing all AddHandler lines and save it back as .htaccess. If that still doesn't work, get a fresh copy of Joomla!, extract it, take its htaccess.txt and upload it to your site as .htaccess. If that still gives you a hard time, uncomment the RewriteBase line and edit it so that it reads

RewriteBase /sandbox
If you have a SEF component (sh404SEF, AceSEF, ArtioSEF, etc), try purging all of its cached URLs, otherwise you may still experience 404's.

-----------------

Local installs can be notorious for not working as expected because they are many times not configured the same way as a server environment. Please do the above and see if that resolves your issues.

user49333
With regards to the configuration.php for $live_site variable. It was blank. I have set it to http://joomla, my local directory which used to bring up my test site using my localhost server. It did not work. Is that the correct setting?

I have renamed the .htaccess to .htaccees.bak and that did not work.

I have saved and uploaded a fresh copy of the htaccess.txt file as .htaccess. That did not work.

I then changed the .htaccess to uncomment the the line and changed the file to read "RewriteBase / joomla" and this did not work.

I have stopped and restarted the apache server and cleared the browser cache after each change.

Please advise. Is there a file I can send you to help trouble shoot this problem?

This is the error I get when I try to load the front end of my local site:
The website encountered an error while retrieving http://localhost/joomla/index.php. It may be down for maintenance or configured incorrectly.
Here are some suggestions:
Reload this webpage later.
HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfill the request.

rkendallc
No. The livesite is incorrect. It should actually be http://localhost/joomla. The localhost HAS to be there. Otherwise, the computer does not know how to access it. That means something to the computer.

You can look for the error log file for your localhost. That would be beneficial. Please attach it to the message. Do not paste it into the copy here. This particular 500 error could be caused by the livesite problem. Please update the livesite to what I gave you above. See if that helps to resolve the issue.

user49333
I renamed the livesite and as recommended and I still get the error.

I have attached the error log showing the last few days since I tried to do the back up restore to my local site. Please advise. Thank you.

user49333
I have done a clean install of Joomla 1.5.23, created a new database and successfully run the kickstart to restore my backup to my localhost but the front end errors out.

I can access the back end with no problem. What is going wrong with this restore?

I have attached a copy of the recent error log file. Please help!

rkendallc
I think the problem may be the kickstart doesn't complete successfully. I am seeing memory limit issues in the log file.

Since you are running on XAMPP, Go to the XAMPP root directory. In there, go to php. Open the PHP.ini file and search for memory_limit. Mine is set to 32MB and it should be set to either 64MB or 128MB. Please check yours and set it to at least 64MB.

Try that and then try to run the restore again with a clean system using the jpa file and just the kickstart. Delete all the tables out of the database since this is local and I assume a development situation. Use Kickstart to restore the files and the database.

Once it completes again, make sure the livesite URL is correct.

If this does not fix the situation, then we'll have to wait for Nicholas. He's not online currently to take a look.

dlb
The 500 error is caused by an out of memory error. It isn't that XAMP isn't allocating enough memory, your site is taking too much memory.

Something that works on your live site doesn't work on your local site. It could be caused by settings in a component that need to be manually adjusted (like VirtueMart) or settings in a bridge to a forum or gallery. These are just a couple of items that require manual adjustment after a restore to a different server because Akeeba can't automatically adjust component's settings for you.

I apologize for being vague, but the error doesn't give much information about what to look for.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user49333
Thank you for the feedback.

The php.ini memory is set to 128MB, so that should not be the problem. The funny thing is, when I was building the my site on cloudaccess.net test site, Akeeba worked fine both ways. Restoring to my localhost and to the test site. After I published my site using my domain name (hosted by cloudaccess.net), the Akeeba application failed.

As for the third party components... this is a very small site. I am very surprised that the restore is failing. The only third party extension that I added was the RS form and Akeeba.

If you need any other log files to help get this resolved, please let me know. I appreciate your help.

nicholas
Akeeba Staff
Manager
Educated guess: You have a Joomla! 1.6 or 1.7 site, which just got restored on your local XAMPP site. However, something is trying to throw an error and the error handling of Joomla! has gone bananas and threw the out of memory errors.

First, I would suggest upgrading your site to the latest version of Joomla!. It's Joomla! 1.5.24 and 1.7.2 for Joomla! 1.5 and Joomla! 1.6/1.7 sites, respectively.

The next thing to do is to go to your back-end, as you said it's working, Global Configuration and set Error Reporting to Maximum, Use GZip Compression to No and Debug Site to Yes. Does it show a different error message that we could probably use to troubleshoot the issue now?

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!

user49333
I'm using Joomla 1.5.23. I will check into upgrading to the 1.5.24 version.

Good news... I changed the Error Reporting to "maximum" and that worked! I can now access my the front end of my localhost site.

Thank you!

nicholas
Akeeba Staff
Manager
You're welcome!

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!

user49333
Good morning,

Unfortunately I just found that only the front page loads. When I clink on any of the other pages/links, I get a 404 Error. Any ideas on what is now causing this problem? Please advise.

I have attached the error log from this morning.

nicholas
Akeeba Staff
Manager
The 404 error means that your .htaccess file does not exist or that Apache's mod_rewrite is not installed. Please check your .htaccess file first.

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!

user49333
Hello Nicholas,

The Apache mod_rewrite is installed and enabled. This was verified yesterday.

As for the .htaccess file, it exists. What am I looking for in the file?

user49333
Here is a copy of the error log. Any ideas?

user49333
Update:

I followed the instruction found here

https://www.akeebabackup.com/documentation/troubleshooter/pr404.html

and extracted the backup files locally, manually copied them over to my local site, ran the restore process "without the kickstart". Then logged into the administration (back end), set the Error Reporting to Maximum and... Walla! It works.

It appears there was something wrong with the kickstart process.

I hope this helps someone else. Thank you.

nicholas
Akeeba Staff
Manager
Well, I have to ask a few questions to understand what happened:
- Which were the exact versions of Akeeba Backup and Kickstart you were using? I was assuming throughout that you were using Akeeba Backup 3.3.4 and Kickstart 3.2
- Which backup archive type were you using? JPA?
- How did you transfer the backup archives (download from old and upload to new server)? Did you use FTP in binary transfer mode? Anything else could corrupt the archive.
- Did you get any error messages during backup, archive extraction or restoration?
Thank you in advance fro providing this optional information. It will allow me to understand the conditions under which this whole thing happened.

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!

user49333
Yes... Backup 3.3.4 and Kickstart 3.2
I downloaded the file using FileZilla FTP (Binary Mode) each time.
I got no error messages during the backup or restoration process.
The only thing I did different was one time I used the kickstart and the second time I did the restore manually.
I hope this helps.

Jim

nicholas
Akeeba Staff
Manager
That's odd! This problem is as if Kickstart wasn't extracting everything from the archive. But given that the same archive, downloaded the same way extracted with eXtract Wizard, it doesn't make any sense; if it was a permissions issue, Kickstart would throw an error. I don't know. Some kind of bad chemistry between your host and Kickstart? Could be. At least you have the tried and tested workaround now :)

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!