gnickoloff

Installed the release, the scheduled time still seems to be somewhat off, but the biggest issue now is the XML export is throwing memory errors now.

[07-Jan-2014 11:58:35] 1. Trying to create a WordPress export to XML file … [07-Jan-2014 16:59:01 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 72632815 bytes) in /home/fjwest5/public_html/wp-content/plugins/backwpup/inc/class-jobtype-wpexp.php on line 123 [07-Jan-2014 11:59:01] ERROR: Allowed memory size of 268435456 bytes exhausted (tried to allocate 72632815 bytes) [07-Jan-2014 11:59:01] Restart will be executed now. [07-Jan-2014 11:59:02] 2. Trying to create a WordPress export to XML file … [07-Jan-2014 16:59:26 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 72632815 bytes) in /home/fjwest5/public_html/wp-content/plugins/backwpup/inc/class-jobtype-wpexp.php on line 123 [07-Jan-2014 11:59:26] ERROR: Allowed memory size of 268435456 bytes exhausted (tried to allocate 72632815 bytes) [07-Jan-2014 11:59:26] Restart will be executed now. [07-Jan-2014 11:59:27] 3. Trying to create a WordPress export to XML file … [07-Jan-2014 16:59:52 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 72632815 bytes) in /home/fjwest5/public_html/wp-content/plugins/backwpup/inc/class-jobtype-wpexp.php on line 123 [07-Jan-2014 11:59:52] ERROR: Allowed memory size of 268435456 bytes exhausted (tried to allocate 72632815 bytes) [07-Jan-2014 11:59:52] Restart will be executed now. [07-Jan-2014 11:59:53] 1. Trying to generate a manifest file … [07-Jan-2014 11:59:53] Added manifest.json file with 7.26 kB to backup file list.

Not sure what is going on here.

I see the backup job ran without error on 12/13 and 12/14 on the most problematic site and successfully on all the other affected sites on 12/15 and 12/16 also, so it seems that the S3/curl problem may have “taken care of itself”. (?)

But when I look at the plugin Dashboard, I see that the next scheduled run time is 12/31/69 leading me to believe that the WPcron config. for this plugin is somehow corrupted.

In the Job Schedule settings, it appears that the values are correct and when I save the settings as-is, the Dashboard once again reflects the correct setting.

It will be interesting to see how this performs overnight now that the Scheduling settings are restored.

OK. Any idea when the next release will happen or any ideas how to troubleshoot/repair the problem until then?

I’m not aware of any PHP update since September Seems to be running 5.4.21. The cURL is version 7.24.0 so that seems to be pretty recent too.

I’m pretty sure the problem is on the remote side but the server support folks don’t agree yet.

Have there been other instances of this behavior?

Wow! So helpful! That’s one of the things I love about WordPress….

Just thought I’d “bump” this thread… I could use the image re-sample function.
Thanks for great work!

Seems to be working fine now.

Not sure how/why, but to “fix it” I changed all the file and directory permissions to 777 and then changed the directories back to 755, and the individual files to 644–which is what I thought everything was set to to begin with, but there must have been some kind of inconsistency in there somewhere… I never did find anything as far as “hosting configuration” problems, etc.

Nice plugin. Thanks.

Seems to be a permissions thing. What are the permissions that you recommend?

I opened up the permissions on the folder, and it is working now. What I don’t get is that “regular” posts (and associated image inclusions, uploads, etc.) were working fine, but not the image uploads with comments….

Thanks for following up with me on this.