motogfx

This is what our host told us after working on it for a few hours yesterday.

Hello,

I have checked into and it seems to be an issue with the plugin you are using. The I/O usage is reaching its limit when the plugin is in process. Also the memory usage at this time seems to be high which prevents the plugin from creating backup of the account. We are currently using Cloud Linux in all our shared hosting plans which limits your resource usage(CPU, Simultaneously running php scripts, Cron jobs etc.) We have this system implemented in order to prevent one account from overloading the server and thus affecting other accounts on the same server.

If there is anything else, please let us know.

The host we’re using added a line to the .htaccess file to lengthen the time but it didn’t seem to fix.

When it performs the initial scan, it shows a warning on large file size. I believe its close to 500mb. So in settings we have enabled SQL dump and “Attempt to keep network alive”

The following error occurs during Building Package:

“Server Status: 500 -Internal Server Error
Error Message:
Request Timeout
This request takes too long to process, it is timed out by the server. If it should not be timed out, please contact administrator of this web site to increase ‘Connection Timeout’.”

The following is the log:

********************************************************************************
PACKAGE-LOG: 2014-12-15 18:58:13
NOTICE: Do NOT post to public sites or forums
********************************************************************************
VERSION: 0.5.8
WORDPRESS: 3.5.1
PHP INFO: 5.3.29 | SAPI: litespeed
SERVER: LiteSpeed
PHP TIME LIMIT: (0) no time limit imposed
PHP MAX MEMORY: 5000M (128M default)

********************************************************************************
DATABASE:
********************************************************************************
BUILD MODE: MYSQLDUMP
MYSQLDUMP: Is Supported
MYSQLTIMEOUT: 5000
TABLES: total:21 | filtered:0 | create:21
FILTERED: []
RESPONSE: Ran from /usr/bin/mysqldump
SQL CREATED: blahblahblahblah_database.sql
SQL FILE SIZE: 28.97MB
SQL RUNTIME: 66.16 sec.

********************************************************************************
ARCHIVE (ZIP):
********************************************************************************
ARCHIVE DIR: /home/blahblahblah/public_html
ARCHIVE FILE: blahblahblah_archive.zip
FILTERS: *OFF*
DIRS: not set
EXTS: not set
—————————————-
COMPRESSING
SIZE: 493.11MB
STATS: Dirs 318 | Files 4,380 | Links 0
SQL ADDED: blahblahblah_database.sql
WARNING: Unable to zip directory: ‘/home/blahblahblah/public_html’

Yes thank you amir did a fantastic job fixing it…and promptly!