reported failures and timeout errors, though none happen (?!)

Resolved rphair
(@rphair)

9 years, 1 month ago
We are getting this error building a Duplicator package on a nearly new WordPress installation, on an AWS (EC2) host where resources are abundant & no confining timeout limits are set:
```
Build Interrupt The current build has experienced an issue.
    Please try the process again.

    Details
    Server Status: 200 -OK
    Error Message:

    Notice
    Build Folder: /var/www/html/cc/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 fiPlease let me know what the next step in our investigation might be...le 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 used Duplicator, both building and installing from the archive files, on a number of web sites of all sizes on this server for at least a year. I’ve only seen this error today, setting up a new site with the most recent versions of WordPress (4.1.1) and Duplicator (0.5.12). The site getting these errors is still new & tiny: less than 400K MySQL database, 2 empty pages, 2 images.

Our server is quiet, not shared, not running low on disk space, plenty of memory, and no load issues (Apache 2.4.10 and PHP 5.5.21). “apache2handler” shows, under Timeouts, “Connection: 60 – Keep-Alive: 5” not suggesting that we are getting timed out at all. “mysql.connect_timeout” is set to 60. php_value max_execution_time is set to 30 – probably not the cause of it failing within 2 seconds.

As the FAQ (http://lifeinthegrid.com/support/knowledgebase.php?article=12#faq-package) suggests I’ve also ticked “Archive Flush: Attempt Network Keep Alive (recommended only for large archives)” about half-way through our testing process, which had no effect. Likewise with “Use mysqldump (recommended for large databases)”.

Duplicator returns with a “timeout” error about 2 seconds after I hit the “Build” button, every time. I can see that installer.php and archive.zip files are being generated in /var/www/html/cc/wp-snapshots/tmp but have no way of knowing if they’re complete. The log file always ends with these lines:
```
********************************************************************************
    MAKE INSTALLER:
    ********************************************************************************
    Build Start
    Build Finished
    Preping for use
    Template parsed with new data
    Complete /var/www/html/cc/wp-snapshots/tmp/cc20150314setup_5504488e956931474150314144118_installer.php]
    Added to archive

    ********************************************************************************
    INTEGRITY CHECKS:
    ********************************************************************************
    SQL File: 381.61KB
    Installer File: 316.84KB
    Archive File: 6.23MB
```
Questions:
1. Can the reason for the reported failure be determined from our log files somehow, even though they show no errors or warnings?
2. How can I determine if the archive & installer files are complete? We’re using Duplicator for site backup & it’s impractical to test every pair of files by building a new site with them.
3. How can we continue our investigation of the problem?
https://wordpress.org/plugins/duplicator/

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

Thread Starter rphair
(@rphair)

9 years, 1 month ago

A further note: I tried this again on a site that is living longer than usual on the same web host (our development server), which has also been automatically upgraded to WP4.1.1 (though it is still on an older version of the Duplicator plugin, Version 0.5.10).

We are getting the exact same error on the second site a well-developed site, but still not huge: a report of failed package generation, though the logfile reports the package files were generated fine.

On this second site, several Duplicator backups have already been made in older versions of WordPress. There are many reports that Duplicator plugin is working perfectly on WP4.1.1, but we still really need to know why the plugin is no longer working anywhere on our development server.

What can we check besides the logfile and the information already reported above?

Cory Lamle
(@corylamleorg)

9 years, 1 month ago

Hi rphair,

I think this might be related to a missing extension. Can you check and see if you have support for mbstring enabled?
Thread Starter rphair
(@rphair)

9 years, 1 month ago
dear Cory: thank you so much for tuning in and for providing and supporting such a great plugin. Yes, you are right, the default PHP installation on Amazon EC2 was missing mbstring. I’ve installed it and now the Duplicator packages are building properly with no errors.

BTW for others on AWS Amazon Linux: this is done by adding the package according to your version of PHP, e.g.:
```
php56-mbstring
php55-mbstring
php54-mbstring
php-mbstring
```
Web server also needs to be restarted afterwards.
Thread Starter rphair
(@rphair)

9 years, 1 month ago

Marking as resolved, also noting that other solutions are concurrently being posted for variations of this same problem.

Cory Lamle
(@corylamleorg)

9 years, 1 month ago

Thanks for the update.

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

The topic ‘reported failures and timeout errors, though none happen (?!)’ is closed to new replies.

Tags