Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #32702
    Declan Dempsey
    Guest

    Hello

    I am an administrator for the above website, pico-play.com . I recently ran into some trouble with updating some plugins, and as such I wanted to restore an earlier backup. I have tried to restore from a archived backup multiple times and via a few different methods – these things keep happenining:
    1. Whenever I click ‘restore’ it only shows a small grey loading circle briefly for a few minutes, then proceeds to do nothing and does not load the page again or restore anything.
    2. Whenever I try to download the file (about 1.5gb) the downloaded abruptly stops at 500mb and does not finish the download.
    3. The same thing happens in #2 whenever I generate a download link and attempt to download it from there.

    Any assistance would be greatly appreciated in how I would go about restoring this backup.

    Thanks,

    Declan

    #32709
    Jesse Owens
    Keymaster

    Hi Declan-

    I’m sorry to hear about the troubles restoring your website, we’ll be happy to help.

    The first thing to check on is the restoration logs for the failed attempts. Navigate to Total Upkeep > Tools > Logs and look for the log with a filename similar to restore-XXXXXXXX.log and a timestamp corresponding to the restoration that failed.

    If you can paste that log here, we’ll be able to determine what’s causing the failure.

    You also might be able to restore your backup using Total Upkeep’s command line utility.

    The issues downloading your backup both sound like they might be related to your server’s LimitRequestBody (if you’re using Apache) or client_max_body_size (if you’re using NGINX) setting. Since they’re stopping right at about 500MB I’d suspect that your server has this setting set to around that amount. Your web host or system administrator may be able to assist you adjusting that. Alternatively, you can use FTP to download the backup file.

    #32728
    Declan Dempsey
    Guest

    Dear James

    Thank you for your response. Below is from the log that is titled ‘restore-1609807703.log’

    [2021-01-05 00:48:23 UTC] Last error: Array
    (
    [type] => 16384
    [message] => add_option_whitelist is deprecated since version 5.5.0! Use add_allowed_options() instead.
    [file] => /home/[redacted]/public_html/wp-includes/functions.php
    [line] => 4859
    )

    [2021-01-05 00:48:23 UTC] PHP Version: 7.4.13
    [2021-01-05 00:48:23 UTC] WordPress Version: 5.6
    [2021-01-05 00:48:23 UTC] Total Upkeep version: 1.14.10
    [2021-01-05 00:48:23 UTC] Restoration process initialized.
    [2021-01-05 00:48:23 UTC] Memory usage – limit / current / peak memory usage: 1024M / 113186880 (107.94 MB) / 113208264 (108 MB)
    [2021-01-05 00:48:23 UTC] Restore info: Array
    (
    [mode] => restore
    [dryrun] =>
    [filename] => boldgrid-backup-www.[redacted].com-695d40b5-20201222-225403.zip
    [filepath] => /home/[redacted]/boldgrid_backup/boldgrid-backup-www.[redacted].com-695d40b5-20201222-225403.zip
    [filesize] => 1678132315
    [archive_key] => 1
    [restore_ok] => 1
    )

    [2021-01-05 00:48:31 UTC] Unzipping archive… filepath / ABSPATH: /home/[redacted]/boldgrid_backup/boldgrid-backup-www.[redacted].com-695d40b5-20201222-225403.zip / /home/[redacted]/public_html/
    [2021-01-05 00:48:31 UTC] Memory usage – limit / current / peak memory usage: 1024M / 113192176 (107.95 MB) / 113222032 (108 MB)
    [2021-01-05 00:50:24 UTC] Last error: Array
    (
    [type] => 2
    [message] => mkdir(): File exists
    [file] => /home/[redacted]/public_html/wp-admin/includes/class-wp-filesystem-direct.php
    [line] => 545
    )

    [2021-01-05 00:50:24 UTC] Signal received: 15 {“signo”:15,”errno”:0,”code”:0}

    I hope this is the what you are after.

    Regards,

    Declan

    #32736
    Jesse Owens
    Keymaster

    Hi Declan-

    Thanks for that! This does give us a couple pieces of good information.

    The very last line, Signal received: 15 tells us that your server sent a “kill” signal to the restoration process- 15 is SIGTERM in Linux jargon.

    The other thing that jumps out at me is that the kill signal came 2 minutes and 1 second after you started your restoration. My guess would be that your server automatically terminates any process that runs for longer than 2 minutes.

    So, with that in mind, there’s a couple of ways we might be able to get your site back up and running.

    First, if you’re certain that it was just a plugin update that caused the issues with your site, you might consider trying the WP Rollback plugin to revert the individual plugins to the previous version.

    Another possibility is using the command line restoration tool, because it will run much faster than restoring through your WordPress Dashboard.

    Third, you can try contacting your hosting provider to see if they can change the 2-minute limit. It’s possible that it might be your PHP max_execution_time setting, but I think it’s more likely that your server has some other system enforcing that limit, because exceeding the PHP max_execution_time wouldn’t normally send a kill signal.

    Moving forward in the future, I’d recommend excluding the /wp-content/uploads/ directory from your backups, which is usually the source of a large backup file. That will give you backups that you’ll be able to easily restore in case of any more issues. Then you can take a separate backup of your uploads folder once per month or so to protect your images.

Viewing 4 posts - 1 through 4 (of 4 total)
  • The topic ‘Total Upkeep Restore’ is closed to new replies.