Duplicator scan running too long.
-
I am running on Siteground. Initially the scan ran in seconds. After install their wild card ssl with dedicate ip the scan runs until it times out. I have a case open with them but am wondering if there ideas on this end.
-
Reply from Siteground Level 2 support:
Checking at the reported issue and the server logs, it simply seems that the plugin can not complete the scan within the server execution_time_out limit and indeed it seems to be some how related to the WildCard plugin and the symlinks that are being created as part of it:
Code:
[Tue Nov 01 11:58:19.900088 2016] [:warn] [pid 18985] [client 87.118.135.129:46972] Timeout waiting for output from CGI script /home/alexa202/public_html/www/wp-admin/admin-ajax.php, referer: https://www.plymouthcountybeekeepers.org/wp-admin/admin.php?page=duplicator&tab=new2
[Tue Nov 01 12:48:31.995236 2016] [:notice] [pid 52What I did and it seems to have temporary solved the problem is:
1. Added the following line into your .htaccess file –>
Code:
SetEnvIf Request_URI “admin-ajax” DynamicTimeout=240
2. Removing the plymouthcountybeekeepers symlink from the domain document root folder as it seems that it was causing a constant loop in the plugin scan process.
As a result I was able to complete the scan process:
My advise would be to get in touch with the plugin developers so they can advise if the mentioned symlink, could be causing a constant loop during the scan process as at the moment the website does load properly but this is due to the fact that it works over www, thus the plymouthcountybeekeepers symlink is not required.
I also noticed that after the can process is completed, an error regarding a script that is not responding is returned:
Can you please try re-installing the plugin contacting the plugin developers as well so they can advise if the mentioned symlink, could be causing a constant loop during the scan process as at the moment the website does load properly but this is due to the fact that it works over www, thus the plymouthcountybeekeepers symlink is not required.
Best Regards,
Deyan Serkov
Senior Technical SupportReply from Siteground Level 2 support:
Checking at the reported issue and the server logs, it simply seems that the plugin can not complete the scan within the server execution_time_out limit and indeed it seems to be some how related to the WildCard plugin and the symlinks that are being created as part of it:
Code:
[Tue Nov 01 11:58:19.900088 2016] [:warn] [pid 18985] [client 87.118.135.129:46972] Timeout waiting for output from CGI script /home/alexa202/public_html/www/wp-admin/admin-ajax.php, referer: https://www.plymouthcountybeekeepers.org/wp-admin/admin.php?page=duplicator&tab=new2
[Tue Nov 01 12:48:31.995236 2016] [:notice] [pid 52What I did and it seems to have temporary solved the problem is:
1. Added the following line into your .htaccess file –>
Code:
SetEnvIf Request_URI “admin-ajax” DynamicTimeout=240
2. Removing the plymouthcountybeekeepers symlink from the domain document root folder as it seems that it was causing a constant loop in the plugin scan process.
As a result I was able to complete the scan process:
My advise would be to get in touch with the plugin developers so they can advise if the mentioned symlink, could be causing a constant loop during the scan process as at the moment the website does load properly but this is due to the fact that it works over www, thus the plymouthcountybeekeepers symlink is not required.
I also noticed that after the can process is completed, an error regarding a script that is not responding is returned:
Can you please try re-installing the plugin contacting the plugin developers as well so they can advise if the mentioned symlink, could be causing a constant loop during the scan process as at the moment the website does load properly but this is due to the fact that it works over www, thus the plymouthcountybeekeepers symlink is not required.
Best Regards,
Deyan Serkov
Senior Technical SupportHey @cyouse
We have seen issues on some systems where symlinks do run forever, however it does seem sporadic and we haven’t been able to to trace why some systems do this. We may have to place an option in the scanner for symlinks to be skipped.
Thanks
I am in tough spot. I can’t back up my site because of it and I depend on the duplicator. It looks like it creates a recursive situation with no bailout hook. The symlink points to the folder where the symlink is.
Light dawns on head of marble. The work around for this problem is to simply add the symlinks to the file filter…
Thanks for the update! That is correct, sorry I forgot to mention that, right now with what I recall we had looked at this issue a before and there was not a good way to do this at run-time it had to be pre-filtered (just as you had done). There may be a situation where we can at least have a scan on a different page that will allow users to spot symlinks that are recursive…
The plymouthcountybeekeepers symlink causes the scan to loop recursively even when it is placed in the file filter list. The www symlink does not. I post the reply below with siteground. This is a serious issue that renders the duplicator plugin unusable by anyone who has wild card ssl at siteground because the symlinks are the smoke and mirrors that allow users to enter all variations of the url with and without www using either http, https or neither and be redirected to the site.
Case reply posted to siteground:
Level 2 support required. The plymouthcountybeekeepers symlink causes the duplicator to go into a recursive loop even if it is referenced in the duplicator file filter list. It is recursive because it is in the the folder that it points to. The www symlink does not cause this problem because it not recursive. The plymouthcountybeekeepers symlink is necessary because without it the site is inaccessible when accessed using just plymouthcountybeekeepers.org without www. I had to delete the plymouthcountybeekeepers symlink to get a duplicator backup to complete.
Is there a way of using a rewrite rule to direct a plymouthcountybeekeepers.org.https://plymouthcountybeekeepers.org and https://plymouthcountybeekeepers .org requests to https://www.plymouthcountybeekeepers.org?
If not I will have to have the plymouthcountybeekeepers recreated because the users are complaing that plymouthcountybeekeepers.org requests fail.
Hey @cyouse,
If you want to submit a support ticket I can have a look in more detail, please refer to this thread in the ticket…
Thanks
- The topic ‘Duplicator scan running too long.’ is closed to new replies.