Hey @mariedi,
It looks like your running into a possible timeout issue on your web server. This usually happens when the server your on terminates the PHP process before it can complete. Its typically more common on budget hosts with larger WordPress sites. Here is a helpful section on the FAQs page that might provide you some workarounds:
– What can I try for Timeout Issues?
– https://snapcreek.com/duplicator/docs/faqs-tech/#faq-trouble-100-q
For quick solutions skip down to the section titled “MANUAL TIMEOUTS WORKAROUNDS”.
Also the latest version 1.2.18 has instructions for a Two-Part Install if the site is too large to zip up…
Let me know if that helps~
The server doesn’t say it’s timing out, it says SCAN RESULT FILE NOT FOUND.
Also, I backed-up the same site (which hasn’t grown in size) multiple times (like I said in my post) and the last time was a month ago without EVER any problem.
Also, I did change the settings (I’m hosted on Hostgator) as per your instructions before I came here for help.
So why is it not finding the scan result file?
What has changed in WP 4.8.1. that would have changed where your plugin can put the scan result file?
The server doesn’t say it’s timing out, it says SCAN RESULT FILE NOT FOUND.
Also, I backed-up the same site (which hasn’t grown in size) multiple times (like I said in my post) and the last time was a month ago without EVER any problem.
Also, I did change the settings (I’m hosted on Hostgator) as per your instructions before I came here for help.
So why is it not finding the scan result file?
What has changed in WP 4.8.1. that would have changed where your plugin can put the scan result file?
Hey @mariedi,
Not 100% sure what the issue might be. If you can give the developer version a try it may have the updates for your issue. We have a patch in that version that helped another user with a scan issue they were running into, do to how their host had things configured. The very latest version (1.2.19) can be found by following these instructions:
> Download Latest Version
> Uninstall your current version and install this one.
If that doesn’t solve the issue, feel free to submit a support ticket here, and we can take a look at your setup if you want… Go ahead and refer to this thread in the ticket…
Thanks
Hi Cory,
Before I saw your answer, two things happened.
1. Because Duplicator was in fact creating a packet and an installer, always of the same size, every time I tried to backup, I decided to install that on a virgin website and guess what? it worked! The site created from that supposedly incomplete duplication is fully functional.
2. And that’s even stranger. In the meantime you issued an update, which I rolled in.
And NOW it’s telling me I need to do a two-part install or reconfigure settings on the server…
It’s the SAME site that I backed-up last month without any problem, the EXACT same site I created packets with a couple of days ago which generated the “Can’t find Scan result file” message but still created the packet and instaler.
So that begs the question: why is this pluging doing worse now than it did in July?
I hope you find the answer!
Marie
One more thing: The end-all error message is still “Scan result file not found”.
So I went and downloaded the log file. When I check the log file of the actual duplication processe, there is NO ERROR!
And again, despite the message telling me the duplication cannot be done, it IS DONE.
Twice today with your new version (1.2.18). So the point really is NOT the creation of the packet, but it’s analysis and location by your plugin (I think).
I think I’ll wait for your answer on this before installing a developper version on a live site… 🙂
Hi @mariedi,
Why is this pluging doing worse now than it did in July?
A few reasons:
1. Basically what happens if your on a shared budget host is that if you have multiple process or resource contention at certain times then the plugin will technically “behave worse” because the host is not allocating the resources that others can be using on that server.
2. The first time you build a package in a given time-frame determined by your host (say every few hours) the file build list and the files that are archived are cached by PHP. So the first run you make on some servers can be very slow. After trying the second time the file info is cached into PHP memory allowing it to be faster. This is not true for all hosts but is common.
3. If your site (Files/DB) are growing in size then you maybe up against a timeout threshold imposed by your host, so if it worked last week at 150MB but you have a very limited host then simply bumping it upto 160MB maybe the catalyst that causes it to start failing. This is usually when we recommend a timeout work-around check.
As I mentioned above if you want us to take a look at your setup we can assist in that manner as to why the scan file issue is happening, at this point I’m not really sure why that is happening in your environment….
Thanks
Cory
hours? No! This is a matter of seconds!
And the site DID NOT GROW in size from July to August.
And I’ve used Duplicator without ANY problem until this week (and your new versions), so I doubt very, very much my host is the problem here.
Especially since I DO END UP WITH WORKING PACKETS but your software seems to thing they are not or they don’t exist.
It’s like when the packet creation process is complete, Duplicator understand that the process has been interrupted by the server instead of having been completed.
I repeat: I DO END UP with WORKING COMPLETE PACKETS.
If I do not believe your software that the process was interrupted by the host and I go back to the packets list, I see the packets with their installer and I did install one of them and I got a FULLY FUNCTIONAL and complete site redeploy!
So I honestly think this has to do with the plugin dealing with the end-of-process (most likely WHERE it’s looking for the file: wp-snapshots/tmp instead of wp-snapshots?) rather than the host interrupting.
Please investigate that and if you find nothing I’ll open a ticket and give you access to the site.
Here is what the log says (partial only, of course):
ARCHIVE RUNTIME: 14.78 sec.
INTEGRITY CHECKS:
********************************************************************************
SQL File: 2.12MB
Installer File: 430.98KB
Archive File: 84.11MB
The log (and reality) says everything went smoothly. Only the plugin seems to think the archive has not been created when it has.
Hey @mariedi,
My only guess is that it may be related to a permissions issue, but that is just a guess. I’m not really sure what the issue is to be honest. At this point I would simply be making guesses as to what might be happening.
You could be right on point, that its something with the newer version that is having interference on your setup but as I mentioned its difficult to guess what the issue might be, I really don’t know, I’m simply just trying to help out were I can. WP sites can get very complex so its impossible for us to know all the variables of your site and setup.
There are over 1 million active installs and we haven’t had any other reports of this issue. We also run unit tests across a dozen different servers/hosts and haven’t seen any issues on our tests. There really isn’t anything for us to investigate as we can’t reproduce the issues your seeing…
If you want to grab an older copy of the plugin you can do that here as well:
https://snapcreek.com/duplicator/docs/changelog/?lite=1
Sorry but I don’t really have to much more to offer…
Thanks
