• Resolved neotechnomad

    (@neotechnomad)


    I am using this plugin, BackWPup (https://wordpress.org/plugins/backwpup/), to backup my site. After the last update, I am getting this message from the backup plugin…

    "WARNING: File path "wp-content/plugins/woocommerce/packages/woocommerce-admin/dist/analytics-report-categories~analytics-report-coupons~analytics-report-customers~analytics-report-dow~99eefb40/style.css" is too long to be saved correctly in TarGz archive!"

    It seems that the string is too long to compress in TarGz and is being ignored, and therefore it not in the backup.
    The plugin uses TarGz to compress to send to Dropbox.
    Could you investigate, please?

    • This topic was modified 4 years, 4 months ago by neotechnomad. Reason: spelling
Viewing 5 replies - 1 through 5 (of 5 total)
  • Rynald0s.a11n

    (@rynald0s)

    Automattic Happiness Engineer

    Thread Starter neotechnomad

    (@neotechnomad)

    This does not seem to work on a site with Woocommerce.
    I ran the plugin four times over the last three days and it always stalls at 78% or 79% and does not go any further.

    Here is the backup plugin’s log file from 2020-06-07…
    (Prior to this, the host’s techs increased the memory limit to 1024MB to see if it would resolve the issue. As you can see, it did not.)

    [INFO] BackWPup 3.7.1; A project of Inpsyde GmbH
    [INFO] WordPress 5.4.1 on https://pinballmedics.ca/
    [INFO] Log Level: Normal (translated)
    [INFO] BackWPup job: PMDailyBackup
    [INFO] Logfile is: backwpup_log_757318_2020-06-07_05-30-33.html
    [INFO] Backup file is: backwpup_DK4ZWV3B01_2020-06-07_05-30-33.zip
    [07-Jun-2020 05:30:33] 1. Try to backup database …
    [07-Jun-2020 05:30:33] Connected to database pinballm_PM7NgOEJi358QT03w on localhost
    [07-Jun-2020 05:30:40] Added database dump "pinballm_PM7NgOEJi358QT03w.sql.gz" with 3.35 MB to backup file list
    [07-Jun-2020 05:30:40] Database backup done!
    [07-Jun-2020 05:30:41] 1. Trying to make a list of folders to back up …
    [07-Jun-2020 05:31:17] Added "wp-config.php" to backup file list
    [07-Jun-2020 05:31:17] 514 folders to backup.
    [07-Jun-2020 05:31:18] 1. Trying to generate a file with installed plugin names …
    [07-Jun-2020 05:31:18] Added plugin list file "Pinball-Medics.pluginlist.2020-06-07.txt" with 3.03 KB to backup file list.
    [07-Jun-2020 05:31:18] 1. Trying to generate a manifest file …
    [07-Jun-2020 05:31:18] Added manifest.json file with 3.68 KB to backup file list.
    [07-Jun-2020 05:31:18] 1. Trying to create backup archive …
    [07-Jun-2020 05:31:18] Compressing files as ZipArchive. Please be patient, this may take a moment.
    [07-Jun-2020 07:03:36] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [07-Jun-2020 07:03:48] 2. Trying to create backup archive …
    [07-Jun-2020 07:09:16] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [07-Jun-2020 07:09:16] 3. Trying to create backup archive …
    [07-Jun-2020 07:14:54] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [07-Jun-2020 07:15:06] 4. Trying to create backup archive …
    [07-Jun-2020 07:34:28] ERROR: Aborted by user!
    [07-Jun-2020 07:34:28] One old log deleted
    [07-Jun-2020 07:34:28] ERROR: Job has ended with errors in 7435 seconds. You must resolve the errors for correct execution.
    [07-Jun-2020 07:35:47] WARNING: ZipArchive::close(): Renaming temporary file failed: No such file or directory
    [07-Jun-2020 07:35:47] ERROR: Aborted by user!
    [07-Jun-2020 07:35:47] WARNING: ZipArchive::close(): Renaming temporary file failed: No such file or directory
    [07-Jun-2020 07:35:47] ERROR: Job has ended with errors in 7514 seconds. You must resolve the errors for correct execution.
    [07-Jun-2020 07:35:47] ERROR: Aborted by user!
    [07-Jun-2020 07:35:47] ERROR: Job has ended with errors in 7514 seconds. You must resolve the errors for correct execution.

    …and the email sent to me from backup plugin 2020-06-07

    [07-Jun-2020 07:35:47] WARNING: ZipArchive::close(): Renaming temporary file failed: No such file or directory
    [07-Jun-2020 07:35:47] ERROR: Aborted by user!
    [07-Jun-2020 07:35:47] WARNING: ZipArchive::close(): Renaming temporary file failed: No such file or directory
    [07-Jun-2020 07:35:47] ERROR: Job has ended with errors in 7514 seconds. You must resolve the errors for correct execution.
    [07-Jun-2020 07:35:47] ERROR: Aborted by user!
    [07-Jun-2020 07:35:47] ERROR: Job has ended with errors in 7514 seconds. You must resolve the errors for correct execution.

    Today I uninstalled the plugin completely, optimized the database, manually checked the database for any of the plugins file (…there were none), reinstalled the plugin and set it for ZipArchive.

    Same result. Plugin stalled at 79% after 193 seconds and did not move.
    (update: at 1365 seconds it is at 80% but still stalled)
    (update: at 1751 seconds it is at 82% but still stalled)

    Two questions:
    1) Is there any other issues such as this from any other users of this plugin?
    2) Could this be only an issue with sites with Woocommerce installed?

    If the answers to these queries are negative, then my only assumption is that this is a problem with the host/server that the site is on… correct?

    • This reply was modified 4 years, 4 months ago by neotechnomad.
    Thread Starter neotechnomad

    (@neotechnomad)

    Update: 4058 seconds and 85%.
    I am aborting the plugin now.
    I am also seriously considering that this is the host’s server issue.

    Hi Neotechnomad,

    I am getting the same issue as you.

    It started happening 2 weeks ago and I can’t resolve it. I’m with Bluehost.

    I updated WordPress to latest version, updated woocommerce,latest bwpup. Hasn’t resolved it.

    I haven’t updated my theme yet and too scared to at this stage as I am unsure how it will affect my site.

    Regards,

    Rzurxn

    Thread Starter neotechnomad

    (@neotechnomad)

    Not using the backup plugin on this site anymore.
    Marking this thread ‘Resolved’.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Code String Too Long To Compress’ is closed to new replies.