• Resolved bennjibee

    (@bennjibee)


    Hi

    I keep getting an error when using duplicator on some dev sites. I have a wordpress site in the root folder and then two dev sits located at /hidden/sitename. I ran duplicator on the root site about 3 weeks ago and everything was fine. Since then I have built the 2 dev sites and when I try duplicator on any of them now, the package build just freezes half way through and says

    Build Interrupt
    The current build has experienced an issue.
    Please try the process again.

    Notice
    Build Folder: /home/sitename/public_html/wp-snapshots/tmp
    Some servers close connections quickly; yet the build can continue to run in the background. To validate if a build is still running; open the ‘tmp’ folder above and see if the archive file is growing in size. If it is not then your server has strict timeout constraints. Please visit the support page for additional resources.

    I’ve spent about 2 hours on the phone with godaddy today trying to figure this out and they have done everything they can, increased max_execution_time to 5mins, increased post_max_size to 128M, and a bunch of other stuff and nothing seems to be working.

    Strangest thing is I’ve just tried duplicator on another site that is on a different hosting account but also with godaddy and the same thing is happening.

    What is going on? I can email you the error log if it will help? I’d post it but it says not to on the error message!

    Cheers

    https://ww.wp.xz.cn/plugins/duplicator/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Hey bennjibee,

    Checkout this question on the FAQs page I believe it may help or provide some clues about this issue:
    -> Browse to: http://lifeinthegrid.com/duplicator-faq
    -> Find section: “Timeout Issues”

    On some budget hosts you can easily run up against time constraints… How big is the site that your trying to build a package against?

    Hope that helps!

    Thread Starter bennjibee

    (@bennjibee)

    Hi Cory

    Ok so I have followed all the php timeout advice on that page. I just tried to address the webserver timeout advice but I’m not sure if I’ve adjusted the .htaccess file correctly. Here is what I have put –

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /hidden/NPM/
    RewriteRule ^$ – [E=noabort:1]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /hidden/NPM/index.php [L]
    </IfModule>

    # END WordPress

    I replace

    RewriteRule ^index\.php$ – [L]

    with

    RewriteRule ^$ – [E=noabort:1]

    Is this correct?

    Thread Starter bennjibee

    (@bennjibee)

    It’s 175mb in size. Here’s the error message –

    ********************************************************************************
    PACKAGE-LOG: 2015-03-30 16:13:23
    NOTICE: Do NOT post to public sites or forums

    [moderated]

    Hey Bennjibee,

    Be sure you remove the package above you created from your site, there is some sensitive information in the log above you posted to the forum that you don’t really want online…

    As far as increasing the timeout, I would get with your host or server admin, they will know what constraints where put where and how to adjust them…

    Cheers~

    Thread Starter bennjibee

    (@bennjibee)

    Ooops! How do I remove it? Can’t see a delete button!

    I have been in touch with them and they have increased the timeout to 5 minutes but it still hasn’t worked.

    Can you see from what I have posted what the problem is?

    You might be able to ask a moderator to remove it…

    In your case I would create a directory filter on your images directory or any of the directories that are large that don’t contain core WP files. This way you can get the package to build, then you can manually move over your larger files later…

    Hope that helps!

    I just removed it but that won’t remove it from search engines – these forums are indexed very quickly, so just FYI.

    Thanks for the update!

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

The topic ‘Archive error’ is closed to new replies.