Support

Site Restoration

#22258 Restoration Unsuccessful; Site Unavailable

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 trlbldr on Monday, 16 March 2015 14:01 CDT

trlbldr
 I experienced some major glitches with two extensions I had obtained through Joomla Extensions Directory and, rather than search out all of the extraneous files that may have been left after I uninstalled these items, I decided (in a moment of weakness) to restore my site files and database using the Akeeba backup file I had created just prior to the installations. As I have always done, I removed all site files and folders from the public_html folder and dropped all database tables so that nothing would be overwritten. My folly, I guess, but this has always worked before.

Kickstart kicked the process during file extraction and gave the now familiar message: "Invalid header in archive file, part 0, offset xxxxxxx". I read the "click me now" help link and tried the FTP route. No joy.

I noticed that the file extraction stopped at the libraries folder - all libraries were extracted, but no folder of file after that point.

I attempted to restore the Website (http://www.jrtcllc.com/) using the host-provided backup and restore service. The database tables were restored as were the site folders & files. However, the site is blank. I manually changed the configuration file to show 'developer' errors; following that, a variety of really strange messages have appeared for no apparent purpose. These have included notices of fatal errors due to illegal redeclarations of 'strcasecmp.php' in two libraries (which is normal in my other Joomla sites) and, currently, 'JHtmlBehavior::core not found'.

I installed Akeeba eXtract Wizard and attempted to extract the site from the jpa file. I tried this in dry run as well as, finally, for real. At each occasion, the wizard stopped when attempting to extract logs/rokcommon.php and reported that file as an "Invalid archive format." (Interestingly, the same file - common to Rockett Theme extensions) is present in each of the Joomla site I maintain. Normally, that file is located in the /log folder; BlueHost apparently created the /logs folder for all log files from the primary and subdomains I have.)

I'm stumped. There's a problem somewhere with configurations or settings I have been unable to identify. Any assistance or suggestions you can provide will help me. Thanks!

Don White

tampe125
Akeeba Staff
Hello Don,

just to be recap, you were able to extract your site using Akeeba eXtract or not?
Can you please try to extract the archive using Kickstart locally?
Does it complete?

Do you have a multipart archive? If so, can you please double check if every part is present?

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

trlbldr
1. Restoration using any .jpa backup I have created for at least one month fails to extract once Kickstart or the eXtract Wizard comes to extracting the /logs folder with the rokcommon.php file.

2. I do not have a local server and am not able to use Kickstart locally.

3. No, extraction does not complete.

Thanks,

Don White

Don White

tampe125
Akeeba Staff
I'm very sorry, but I think there are no solutions for your situation.

TL;DR Explanation
Your backup is corrupted: if you can, you should take another backup and exclude both the log and logs folder from your backup.
If you can't take another backup, the only solution is to partially restore your site. Your site will be broken, but at least you can recover the database contents and start from them rebuilding your site

A little more technical explanation
Your backup included a log file, which size changed during the backup process.
If it grows bigger, there are no problems: we will only read the original size when the backup started. If it shrinks, we have problems. In the header we record its original size (let's say 100), then we actually write its contents. If there is less data (let's say 80), when we will restore it, we will read its 80 bytes + 20 bytes of something completely unrelated.
So this is why you got the Invalid header error.

We automatically read Joomla configuration and exclude the log directory (log folder), however it seems that RocketTheme developers are hardcoding the path (logs folder). This means that it's not automatically excluded, leading to the error you reported.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

trlbldr
Davide, thank you. Yes, the jpa backup file is corrupt; I believe it was corrupted by an anomaly with rokcommon.php from the research I cited earlier.

I had specifically selected the contents of the /log folder to be excluded by Akeeba Backup. I did not realize (read the fine print, Don!) that, in the case of a primary domain with active subdomains, the Web host places all joomla log files in one folder, /logs, rather than in the separate /log folder created by Joomla at installation. I am addressing this with BlueHost, but it won't matter with this issue.

I cannot make another or a new backup because the website is blank at both the public front-end and admin backend sites. That's why I pointed out the confusing and disparate error message that point to the probability of a configuration catastrophe, or glitch. The site files and the site database tables were reconstituted using the Web host backup accomplished at 12:59 A.M. on Sunday morning; restoration of those folders, files, and db tables was accomplished yet the site is unavailable.

I have set in motion a support ticket with BlueHost but have heard nothing useful from the company. Yet.

Maybe RocketTheme is responsible for the extraneous /logs folder. I haven't seen that in the single-domain sites I maintain, but it's possible.

Cheers,

Don White

Don White

tampe125
Akeeba Staff
Ok, good luck with your site!

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

trlbldr
Okay, I (finally) got my Website back and it's usable. How? I don't know. Here's what I did, though. I:

  1. Used Akeeba eXtract Wizard to extract the site folders, files, and SQL data recoverable from the JPA file.
    [list=2]
    Dropped all database tables "restored" by the BlueHost backup & restore service.
    [list=3]
    Reconstituted the database tables by importing the SQL files (.sql + parts such as .s01, etc.).
    [list=4]
    Used FireFTP to upload all recovered site folders and files.
    [list=5]
    Drank Scotch.
    [list=6]
    Closed the browser.
    [list=7]
    Removed all cookies.
    [list=8]
    Drank more Scotch.
    [list=9]
    Opened a browser to my site.


  • This worked. I think that the critical elements to recover and reestablish were the:
    [list]
    Admin folder (all contents)
    [list]
    Database (of course)
    [list]
    Includes, Libraries, Layouts folders


By the way, I downloaded and installed FileZILLA, but that installation released Malware onto my laptop (Binki-something). Malware Bytes, Kaspersky, and Revo Uninstaller Pro successfully removed the code, although I had to physically remove the browser extensions in IE11 and Firefox.

Sorry to have taken up your time with this. I guess I blundered into and out of the situation.

Don White

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!