0.5.10 version broken!?

I too had this problem.

My host also said the problem was with the plugin. In my case I had just happened to make a package just before upgrading, used that with no issues.

I too think this plug in is awesome and have used it multiple times!

Hey design_studio,

Thanks for the feedback! Do you recall if you were using the database build mode ‘PHP’ or ‘mysqldump’? New logic was added to this version which helps create an end of file marker in your SQL file, which requires the SQL file to be read into memory to write the marker. I think this may be causing the issue your seeing, but I need to know the DB mode as that will help me isolate the issue…

Thanks

Hi there, thanks for answering so quickly. What is shown on the Scan page is Build Mode: PHP (slow). What I’ve also found in the settings page is:

Database Build
This server does not have shell_exec configured to run.

I am not sure if I must have this enabled, so I’ll get in touch with the hosting to discuss if I they can enable this feature. I suppose however for mysqldump to run.

Thanks.

OK Thanks… I’ll see if I can get out another version shortly to address the low memory bound settings… If you want to submit a support ticket I can have a deeper look at your setup. Right now its very difficult with some hosting companies to work within such tight configuration constraints. Which means even the smallest features can break things on some servers…

Cheers~

Hey design_studio,

There is a new setting in the Developer version, under the Settings menu, its called Query Limit. This should help to conserve memory if you having memory issues when using the PHP mode. Try and set this to it’s lowest setting if you have any memory issues. The very latest version (0.5.11) can be found by following these instructions:

-> Browse to https://www.ads-software.com/extend/plugins/duplicator/developers/
-> Look for the section “Other Versions”
-> Click on “Development Version” and download the zip plugin file
-> Uninstall your current version and install this one

Let me know if this solves your issue…

Thanks

Hello and thank you for all your efforts. Unfortunately this version didn’t work as well. I tried all the options under the PHP settings and I receive one and same error. I leave enough time between the tries to make sure the server is not pushed too much :). I can put the error log here if you want – I replaced the real paths for security reasons.

I am not an expert in anyway, but is there any chance something else to be the reason for the error. I still get the error for max I/O connections reached. Do you think I have to ask the hosting to activate some option which might help?

I’ve just tried the 0.5.8 version and works like a charm.

Thanks again for all the efforts.

P.S. I’ve just made a screenshot of the resource page if you want to see how the resources are used when the plugin works. I can guarantee that there are no visitors or any other activities at the same time. Taking another look to that screenshot myself it looks like 0.5.8 maybe is using more resources than the last version. Then the error might be somewhere else.

And of course this is the completed page (I removed the personal info from it).

That is interesting. That looks like an OS restriction setup by your hosting provider. My feeling is that if your site gets much bigger then you will start to have issues on 0.5.8 as well, because the underlying logic that opens I/O connections is almost identical. You may have to use the older version until you reach an error on it. At that point you may have to create a directory filter on Step 1 of the package creation process to limit the amount of files it is trying to archive.

If you want me to take a deeper look at your system you can submit a support ticket and I’ll take a look at your server, and see if there is a way to get around the hosts setup restrictions.

Hope that helps!

Hello again and thanks for your answer.
Basically 3/4 of the archive size is wordpress files. the rest is mine. Which is like 3-5mb. Anyway, I’ll speak with them again as soon as I can and will see what the outcome will be.

Sounds Good… Thxs for the update.

Hi there,
It took a while but here is the update.

My hosting were very kind and adjusted the amount of memory used (although this wasn’t a problem for all versions up to 0.5.8).
I’ve seen that there is a new version out (0.5.12) so updated it.

It looks that the last 2 versions of the plugin use excessive amounts of memory and other resources (probably some limits must be set)! I don’t know if this is result of the new logic you are talking but it just takes my shared hosting account to its knees.

Unfortunately something doesn’t work again and I get the same error in the front end. However the size of the final archive looks complete (and I have Build Start Build Finished message in the log), so I decided to give it a try and restore it locally in WAMP server.
And everything looks great from the start to finish. With 0.5.10 and 0.5.11 versions the size of the archive was about half of the archive size now.

So locally restored all areas of the website works ok, however I am still not confident enough to do it on the real server and replace the working site. I also noticed in the log that the plugin is unable to set the memory limit again. With kind of no restrictions on this on my hosting it looks like the plugin is not trying to set the limit (not sure if this is the case).

So finally as I said the archive works, but the front end throws an error. And I am sure it is not some kind of a timeout because the old 0.5.8 version takes almost double the time to complete, but there is a successful message and everything works with no problem.

The size of the site to backup is ~53MB. The archive is ~39MB. Basically this is 3/4 WordPress and few extra images.

Kind regards

P.S. I don’t want to sound ungrateful for the great job you are doing. I am just trying to help with that issue to be resolved if possible. But by no means you have to do that. Anyway. Thanks again

Hey Design_studio,

Its no problem… All input is helpful. There was new logic added in 0.5.10 that validates the SQL file was generated correctly, however it should not use up too much memory. Something you might try if your having memory issues is to use mysqldump if its available. If not then you can try to keep the Query Limit really low. Both of these options are in the Settings menu.

If your still having issues feel free to submit a support ticket and I can have a look at your system if you want. If you decide to submit one, please refer to this thread.

Cheers~