Unpacking a 1Mb gzip file would only be expected to take a second or two.
No need to check phpMyAdmin if it says no more than that.
Two possibilities: 1) the web server kills off PHP for running too long, or 2) there’s a problem with the write permissions on the wp-content directory.
I’ll add in an extra check for 2). If you were willing, can you share the backup set with me? Then I can test a migration from here, which will go faster. If sharing via Google Drive (like last time), then it’s best to set the share to be public for anyone with the URL, and email me the URL at contact@updraftplus.com.
David
Hi
I hope you have received my e-mail with the link.
Is it working?
Should we just continue on mail from here on?
Thanks
Nikolaj
Hi Nikolaj,
I got the link, and managed to restore using it. On my laptop (a Pentium – a budget laptop), it needed 63 seconds to run. The ‘unpacking’ step though takes less than 1 second (it’s just uncompressing the 1Mb gzip file).
Is it asking you for filesystem (FTP etc.) credentials before you do the unpack?
Are you comfortable with simple editing of code? If you can, then, before doing the restore, do this:
– go into the WordPress plugins editor (Plugins -> Editor) and choose UpdraftPlus, and edit updraftplus/includes/updraft-restorer.php
– Approximately line 40, there is a line:
$this->skin->feedback('unpack_package');
– Immediately after it, add this new line in:
print_r($wp_filesystem);
Then run the restore, and tell me the output.
Alternatively, if you let me have a login to the site which you’re restoring _to_ (i.e. the destination), then I can iterate a bit faster (contact@updraftplus.com).
David
Hi David
I will give it a go, if this doesn’t work I will provide you the login.
Thanks
/Nikolaj
Hi David
This is what I get:
WP_Filesystem_Direct Object ( [errors] => WP_Error Object ( [errors] => Array ( ) [error_data] => Array ( ) ) [verbose] => [cache] => Array ( ) [method] => direct )
I hope it means something to you.
/Nikolaj
David,
sorry I think I have left out some important information:
“Your web server has PHP’s so-called safe_mode active. This makes time-outs much more likely. You are recommended to turn safe_mode off, or to restore only one entity at a time, or to restore manually.“
Would this explain the error?
Sorry to have left it out to begin with.
/Nikolaj
Hi Nikolaj,
Yes, that’s significant. It causes the timeouts to be lowered, usually too far to make anything work… you need to ask your web hosting company to turn it off… PHP’s safe mode was basically a bad idea, that they recommended people don’t use. Eventually they deprecated it and removed it in the last-but-one version (http://php.net/manual/en/features.safe-mode.php). So it won’t plague our lives again once everyone catches up to recent PHP versions…
And we need to make sure that is logged so that I can spot it earlier!
David
Hi David
Just got a reply from support, saying, they didn’t have plans for upgrading php any time soon and that safe_mode could not be turned off.
So basically with these kind of servers, updraftplus will take a backup (unless the upload folder is filled with lots of small files, max_execution_time is even lower here, 30s??), but will not work to migrate sites?
So nothing more I/we can do to get it working here?
Thanks
Nikolaj
Hi Nikolaj,
We’ve got some plans to break up the ‘restore’ operation into multiple requests so that low timeouts don’t apply to the whole operation (but just to each sub-request), but that’s going to take a while to deliver, I’m afraid… in the meantime you’ll have to restore manually: http://updraftplus.com/faqs/i-want-to-restore-but-have-either-cannot-or-have-failed-to-do-so-from-the-wp-admin-console/
The PHP group deprecated safe_mode when they released PHP 5.3 in June 2009 – http://news.php.net/php.announce/77 ….. to find web hosts still treating it as essential 4 years later… well, make of that what you will…
David
