New S3 Error

  • Hi,

    First I have to congratulate you on Backwpup. One of the better backup plugins I have tested. Since updating to 3.2, I keep getting an error on one of my sites.

    2011-07-16 14:07.56: Add Database Dump to Backup list: vordpress.sql 42.51 MB
    2011-07-16 14:07.56: 1. Try for wordpress export to XML file…
    2011-07-16 14:08.19: Add XML export to backup list: wpj.wordpress.2011-07-16.xml 9.61 MB
    2011-07-16 14:08.19: 1. Try for make a list of files to Backup ….
    2011-07-16 14:08.19: Files to Backup: 8393
    2011-07-16 14:08.19: Size of all Files: 575.06 MB
    2011-07-16 14:08.19: 1. Try to create backup zip file…
    2011-07-16 14:10.51: [ERROR]Maximum execution time of 30 seconds exceeded
    2011-07-16 14:10.51: 1. Script stop! Will started again now!
    2011-07-16 14:10.51: 2. Try to create backup zip file…
    2011-07-16 14:10.51: Backup zip file create done!
    2011-07-16 14:10.51: [WARNING] filesize(): stat failed for /var/www/…

    2011-07-16 14:10.53: [ERROR] Amazon S3 API: The size of fileUpload cannot be determined in create_mpu_object().
    2011-07-16 14:10.53: [ERROR] Step arborted has too many trys!!!

    I have not changed any settings, so I am not sure how this which worked fine for a few months is not doing it. Any suggestions is appreciated ??

Viewing 2 replies - 1 through 2 (of 2 total)

  • the main Problem ist the hit of the Maximum execution time i will make it longer on sip close. it comes with next release.

    Thread Starter WPJEDI

    (@cyrus100)

    Thanks Daniel. You are the best. I was able to run it manually after changing the temp folder to my root address. .com/temp

    But yes. The execution failed a couple of times. I actually got a few Gateway errors when running this manually which is strange on our dedicated server. The funny thing is, your plugin works flawlessly on 2 other sites on the same dedicated server with the exact settings… everything.

    I have to say. Your plugin is one of the best backup plugins I have tested and I have tested many ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘New S3 Error’ is closed to new replies.