Support

Site Restoration

#30690 Only J01 file

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 on Sunday, 13 January 2019 17:17 CST

dpollez
Hi
After uninstalling an extension that I did not need, I had a white screen of death on my Joomla site. I took a backup yesterday and want to restore the site but I only have a .J01 file and not a .JPA file.
What can I do?
Thanks
Didier

dlb
That's not good. The j01 file is no good without the jpa or jps file associated with it. Where are you looking for the files? Was it transferred to a cloud storage location? If so, the jpa file may still be on your site. Either way, this would indicate that the backup did not complete.

There are some troubleshooting tips for white screen errors: A white page or a page with a 500 Internal Server Error is, in fact, either a .htaccess issue to a PHP fatal error in disguise.

First, let's see if it is a .htaccess issue. Try renaming the .htaccess file in your site's root to htaccess.bak If there is a .htaccess file in the site's administrator directory, try renaming it as well. If that solves the problem, the issue was with a directive in your .htaccess file. We'd like to recommend you to try removing directives from your .htaccess until you find the one which causes the problem.

If that doesn't help, the error you are receiving is in fact a PHP error in disguise. First, check your server's error logs (not the access logs) immediately after visiting the page which throws the error. There should be an exact description of the PHP fatal error which occurred. Sometimes you can find the error messages in files called error_log or error.log inside the site's root and/or administrator directories. If unsure about the error log location, please consult your host. Most likely the error logs are available in your site's hosting control panel.

If your host does not give you access to the error logs and you have access to the Joomla! administrator area, please log in to your site's back-end, go to Global Configuration, click on the Server tab and set the Error Reporting to Development. Try visiting the problem page again.

If you still get a blank page, edit your configuration.php file and put the following code right after the final closing curly brace ( this is what a curly brace looks like --> } ) but before the closing PHP tag (it looks like ?> that is a question mark and a greater-than sign):
ini_set( 'display_errors', true );
error_reporting( E_ALL ); 
Try visiting the problem page again.

If you still get a white page, please remove the two lines from your configuration.php file. Edit the .htaccess file in your site's root. If you don't have a file named .htaccess create a new one. Beware that htaccess.txt is a DIFFERENT FILE and will NOT work! Add the following to the end of the file:
php_flag display_errors On
php_value error_reporting 32767
and retry loading the problem page.

If you still get a white page, remove the two lines from your .htaccess file. Now, create a file called php.ini with the following content:
display_errors=on
error_reporting=E_ALL
and upload it into your site's root and your site's administrator directory. Retry loading the problem page.

If that fails again, remove the php.ini file and create a file named .user.ini (note that it's dot user dot ini, the leading dot is important) with the contents:
display_errors=on
error_reporting=E_ALL
and upload it into your site's root and your site's administrator directory. Wait for 10 minutes. Waiting is important, .user.ini files do not apply immediately. Retry loading the problem page.

IMPORTANT: Sometimes the error won't show. Edit your configuration.php and find the line starting with public $error_reporting and set it to:
public $error_reporting = 'development';

This instructs Joomla! to enable maximum error, warnings and notices verbosity. In 99.9% of cases it will result in the error messages being shown on the browser.

If you still get a white page, delete the php.ini or .user.ini file your created and consult your host. They have to provide you the PHP error message, file and line it occurs (along with the error's backtrace) themselves.

Please note that if you can not understand what the PHP error message means, just copy and paste it here verbatim so that we can take a look and point you to the right direction.


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)

dpollez
Thanks, I'll tried already most of what you wrote, still continue trying.
I look at /administrator/components/com_akeeba/backup
And see the following files dated 12/12/2018

akeeba.backend.id12.log
akeeba.backend.log
akeeba.log
akeeba_backend.id121
site-www.oostwaarts.be-20181212-225411utc.j01

I have JPA file one day older, but then I loose one day hard work
How you please send me a link with how to restore a site starting from a corrupted site (deleting all files or not, deleting database or not…)
Thanks for your quick response.
Didier.

dlb
Step #1 - Download the backup archives and store them in safe place(s). You can't have too many copies of your backup. Paranoia is your friend.

To do a clean restore you would delete all of your Joomla! files. This is usually all of the files in www or public_html. But this can change if you have other applications in the same hosting account, another site, a non-Joomla! package like a forum or genealogy application, etc.

You would then drop all of the Joomla! tables in your database. Once again, be careful of non-Joomla! applications if you have any.

Then you would upload your backup archive and kickstart.php (from our Downloads page) and call:
www.mysite.com/kickstart.php
From there, just follow the screen instructions.

***** BEFORE YOU GO BACK A DAY *****
If your day old backup is just one file, a jpa file, it is possible that yesterday's backup is just missing renaming the j01 to jpa. This happens towards the end of the backup process. Rename the j01 to jpa and see if kickstart will extract it. If it really is a j01 and the jpa is missing, that trick won't work so it can't hurt anything.


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)

dpollez
Thanks!
I managed to have the site online again with the help of the extension developer.
And for the bad backup: I guess it went wrong because I switched to another app during backup.
Thanks a lot for your quick and superb help!
Didier.

dlb
I'm glad you got the site back. I'm sorry I couldn't fix it.


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)

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

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!