Backups not completing, even with 40Mb "split" size

The log has this:

memory_limit: 128M (used: 99.9M | 100.5M)

i.e. PHP is set up with a memory limit of 128M, and 100M is already used by other plugins before UD starts. As such, it’s almost certain that it gets killed due to memory exhaustion. You should raise the PHP memory limit.

David

I tried disabling all other plugins and shifting to the Twenty Fifteen theme and the backup still failed. If other plugins were the problem, wouldn’t that have caught it?

Do you know how to set up PHP with a higher memory limit?

Hi, David,

I set up PHP with a 256Mb memory limit. Apparently Updraft tried 9 times and then decided nothing was happening. It then at some point did one more try and apparently stopped with no wrap-up. As you can see in the log file here:

https://dl.dropboxusercontent.com/u/106730/MISC/log.d8ef3b5d68f7.txt

It said:

2792.535 (9) The current run is resumption number 9, and there was nothing useful done on the last run (last useful run: 3) - will not schedule a further attempt until we see something useful happening this time

I’m very puzzled.

Hi,

You can try adding this to your wp-config.php:
define('WP_MEMORY_LIMIT', '256M');

If that doesn’t work, you (or your hosts/server admin) will need to raise the ‘memory_limit’ configuration in php.ini.

Hi. Sorry for the radio silence. I was traveling.

I have raised the WP_MEMORY_LIMIT to 256M, and my PHP.INI says: memory_limit=256M . Updraft still isn’t working.

It may not be the memory limit after all. Is there any way to dig deeper for the diagnosis?

That helped, but now you’ve hit another problem – your PHP install doesn’t have the PHP “ZipArchive” module, and as a result it’s falling back to a much slower solution, which it’s timing out on. You should ask your hosting company to enable the PHP ZipArchive module.

David

I asked my ISP to recompile PHP with ZipArchive and it worked!!! YAY!!! Thank you VERY much!

In trying to reconnect UpdraftPlus to my DropBox, to upload the backups, the authentication has failed with the following error messages displaying on the admin screen:

Warning: openssl_encrypt() [function.openssl-encrypt]: Using an empty Initialization Vector (iv) is potentially insecure and not recommended in /u/s/stever777/websites/www.steverrobbins.com/docroot/wp-content/plugins/updraftplus/includes/phpseclib/Crypt/Base.php on line 1057

Warning: openssl_encrypt() [function.openssl-encrypt]: Using an empty Initialization Vector (iv) is potentially insecure and not recommended in /u/s/stever777/websites/www.steverrobbins.com/docroot/wp-content/plugins/updraftplus/includes/phpseclib/Crypt/Base.php on line 1057

Since these are happening somewhere within the UpdraftPlus codebase, I’m not sure how to proceed. Is there a fix for this, or is this caused by another non-standard PHP setting that I should highlight for my sysadmin?

Thanks,

Stever

I went ahead and hacked around, disabled all warning messages, was able to successfully link to Dropbox, and then re-enabled the warning messages. Once established, the link seems to be working fine.

YAY! I’m now back up and running. Thank you very much.