This does not appear to be a permission issue or space issue exactly even though that’s the error message. Siteground has ran tons of checks and I can actually replicate the issue on demand. If the backup goes above 2GB it fails and gives that error, if it’s below that, it works correctly.
We have checked everything.
1. Verified all files/folders have the recommended permissions for a WordPress site
2. Verified the upload_path value in the database of the site is correct
3. Checked if the feature would work with a different PHP version
4. Verified there are no rules in wp-config.php, php.ini or .htaccess that could affect the creation of the backup
5. The max file size limit is 8GB. ([~/public_html]# ulimit -f
8388608 )
6. The permissions are correct
7. There are no errors in the server log.
8. FYI, I also have another client site also on Siteground with backups in excess of 7GB with no issues. So it could still be siteground for this client but the fact that another client is also hosted here with no issue, makes that less of a chance.
Keep in mind, I have used this plugin for over 2 years on this exact website. I have never had an issue until about 2 weeks ago now and have been working with the hosting support trying to resolve it.
The only error in the all-in-one error log is this:
{“Number”:8,”Message”:”fwrite(): write of 8192 bytes failed with errno=27 File too large”,”File”:”\/home\/SITEHOME\/public_html\/wp-content\/plugins\/all-in-one-wp-migration\/lib\/vendor\/servmask\/archiver\/class-ai1wm-compressor.php”,”Line”:96}
They, and I, am now convinced that 1 of these things is happening:
1. The plugin is being restricted due to a script conflict or error with another plugin even though there are no script errors showing up in the console or logs.
2. There’s a setting some where from the last update of the plugin that has changed and is causing this.
3. There is a PHP or server setting that they are missing that is causing this.
This is as much detail as I have right now. In summary, this absolutely has something to do with the 2GB threshold since I can replicate the issue by forcing the backup above and below this size to make it fail or work accordingly.
-
This reply was modified 4 years, 3 months ago by bilmartech.