Backups with filesize error

Just in case it’s connected, this message appears when “Compressing files as ZipArchive” starts:

Array ( [0] => /home/{path redacted}/wp-content/uploads/backwpup-b89722-temp/domain.sql [1] => /home/{path redacted}/wp-config.php [2] => /home/{path redacted}/wp-content/uploads/backwpup-b89722-temp/AquaCents-Water-Management-For-Turf.pluginlist.2018-11-10.txt [3] => /home/{path redacted}/wp-content/uploads/backwpup-b89722-temp/manifest.json [4] => /home/{path redacted}/wp-content/uploads/backwpup-b89722-temp/backwpup_readme.txt )

BTW, the message above appears even when all other plugins are deativated.

Also tested by rolling back one site to Version 3.6.2, and the error went away. So there is some problem for us in 3.6.3 with filesize. What should we do?

Nevermind on the version difference. The site we rolled back the version on also has this issue.

....
[12-Nov-2018 08:35:24] One file deleted on S3 Bucket.
[12-Nov-2018 08:35:24] One old log deleted
[12-Nov-2018 08:35:24] WARNING: Job finished with warnings in 1940 seconds. Please resolve them for correct execution.
[12-Nov-2018 08:51:16] WARNING: filesize(): stat failed for /home/{pathredacted}/wp-content/uploads/backwpup-b89722-temp/backwpup_WW4JOISL02_1b9224c8c420_weekly_2018-11-12.zip
[12-Nov-2018 08:51:16] ERROR: Aborted by user!
[12-Nov-2018 08:51:16] ERROR: Job has ended with errors in 2892 seconds. You must resolve the errors for correct execution.

Hi @bethannon1,
Really sorry for my delayed response, we were busy prepare for the new plugin update.
About your issue, I want to ask you a few questions:
– Is the issue only happens on S3 destination? Could you try another destination like dropbox? what happens?
– seems irrelevant but could you try with another archive type like Tar?
Thank you!

Thanks for your reply!

One of the problems is that the issue seems very intermittent. There are not consistent sites failing this filesize check, and even different jobs within the same site are not failing with consistency. I’m not able to reproduce this issue regularly with a manual run of the job. So like all inconsistent issues, troubleshooting is difficult.

The problem occurs right after the upload to S3 completes (and the old backup in S3 is deleted).

It seems that the filesize is looking for the .zip file of the backup (see the line for 12-Nov-2018 08:51:16 here). But of course, that file is no longer in the uploads folder because it has just been uploaded to S3. It just doesn’t seem logical to do a file check in that location when the backup just got sent to the remote location.

I know the array that appears on the job running page is a dev tool that got left in. Is there any possibility that the filesize check is something similar?

And, why would the filesize check appear? Because it’s not appearing in the logs that are completing without this warning. So what would be triggering it?

Thanks in advance! Looking forward to the new update. Let me know if you need beta testers!

Hi @bethannon1,
Thank you, we have a beta 3.6.4 in here, could you please test then tell us if your issue has been resolved?
https://www.dropbox.com/s/sqabu59xuwg67cp/backwpup-wporg-3.6.4-RC2.zip?dl=0

I have installed the beta plugin on a half-dozen of our sites that have been regularly having this issue. I will have to come back tomorrow and let you know if they still have the filesize issue. Thanks!

Looks like no errors from those 6 sites. I’ve installed the beta on another 6 sites that have been showing the filesize issue, and I’ll let you know Monday if that also seems to work. If that works, I’ll add the beta to more of our sites Monday.

Just out of curiosity, was the query for the just uploaded .zip file part of the issue?

Update: this morning, there are several sites updated to 3.6.4beta that have backups with the filesize warning. So the beta did not solve the issue.

I am not able to determine any pattern here for why some sites present those warning of filesize error.

Again, it doesn’t seem to make any sense to me that for some reason BWPup is trying to look for the .zip file right after the file has just been uploaded to the remote destination.

Perhaps it might help in trouble shooting if you could tell me what that filesize check is hoping to accomplish and/or what specific situations it gets triggered with?

@bethannon1
I forwarded your issue to our devs, will back to you when I have something new!

Great! Happy to work with them or beta test if needed!

Just FYI: we have updated to 3.6.5 and are still having this issue. A lot.

Anything we can do to help with getting info/resolution on this? It’s happening on both of our VPS servers.

Still doesn’t make any sense to me that the filesize check would happen AFTER the .zip has been uploaded to remote destination and deleted….

Hi @bethannon1,

Sorry for the long delay, we tried to reproduce the problem without success.
We think could be more than one process that run the backup with some run-out seconds that could create the problem.

Do you think could be possible to have the entire log file that show the problem to debug it a bit?

Another try you could do is to use a server cron that call wp-cron script, for more info see https://pressjitsu.com/blog/wordpress-cron-cli/ and set the schedule for the job to run manually only.