-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errorcode 1 with gzip of database dump.sql during database pull #528
Comments
Hi, we cannot provide help about a single hosting company problem since we don't use their service and we have no idea on what's the difference between WPe and the rest of the world :P Would be a good idea to investigate these problems together with @frontenddevguy and @kLOsk (and possibly let only one issue alive) |
It sounds like it could be WPE related, I more put that in just to be inclusive. I can hop over to the issue that appears to be the exact same (I really did try to search and failed miserably on that.) Thanks again!!! Hopefully we find a solution, WordMove is a huge part of my workflow and I miss it! |
I tried talking to WPE support but didn't get far. My overall impression after working on their hosting for a client was that it is not very developer friendly. They also did not support including images in GIT, or webhooks, and refreshing the cache required a request to support. |
I did a little digging and it actually does not appear to be the gzip command causing the issue. If I take line 79 of ssh.rb and duplicate it, I get the same error. I tried a few other things where I would put say just tell @copier.exec! to run some random command first. When I do that it crashes with he same error on a command that just ran.
So for this, the first one runs and the second then errors out
So it looks to have more to do with running more then one command over an existing. If I run it once so that the 'dump.sql' is created and sitting there, then comment out the line that runs that dump and jsut leave 'remote_run compress_command(remote_dump_path)' it will compress the file with no error and then error out on the remote_get command down below:
If I follow the same pattern and remove the 'remote_run compress_command(remote_dump_path)' it will now run the remote_get command and actually get the file. Not sure if this helps at all? |
Apologize for the dirty code in advance: I made a global version of the ssh_options to try something:
Then I updated the 'download_remote_db' to create a new @copier each time around.
That will successfully run. Not sure what that means. But thought I would mention it to see if it means something. |
Nice trip here 🙂 I’ll take a dive for sure, trying to compose an idea from those symptoms. |
Hi @mechdog , would you like to do a first enigmatic test doing
??? I've studied a bit of SSH's protocol behaviour and its asynchronous channels, driven by your inspection. Really don't know if I'm on the right path, but we have to start walking :) Thanks in advance 🙏 |
I sure can. I went ahead and ran that under a a ruby 2.4.1 rvm install so I can swap back and forth as needed for work. It runs to the same error as before. What do you want me to do as the next step? |
Having the same issue on WPE - following :) |
@mechdog simply re-do
version |
Okay. I think I have everything done correctly. Here is the error I'm receiving
|
This was just my distraction. Sorry about that. Latest version is |
Sorry for the delay. So far, it looks like that was the ticket! I'll keep trying it, but I just pulled and pushed with the pre4 addition. The database push back up fails, but I think that is because it is seeing the user as a remote user instead of a local and denying permission. This is a separate issue completely though so I will look into it and open a separate ticket at some point. Thank you!!! |
Ok @mechdog ; thanks for the follow-up. As far as it stands, I'm really happy with our progresses. Would you mind to give a definitive feedback before we'll close the issue? I'll have time to write down something definitive and more polite just on next week and that would be a geat reminder for me :) In the meanwhile you'll have more chance to test and to figure out drawbacks... Lemme know. Thanks again |
I tested on a new area and can confirm that the changes now allow pulling of the information from WPEngine without the error. |
@frontenddevguy and @kLOsk would mind to test this pre-release before I'll go down with a serious write? |
can confirm, pulling db is now working nicely with wpengine and 4.0.2.pre4 |
Ooook, thanks. I'll put my head on this in the next week |
any word on |
Working, using the pre release as explained above! |
Hello there, today we released wordmove 5.0.0; I'd like to take the work of the branch with the patch done specifically for this issue, rebase on latest version and release a This patch is not ready for production, but I want to keep the light on it, test more, understand more and maybe improve the patch itself. In the meantime if I wont rebase and release an ad-hoc version, you all will be bound to an older version. So far so good, but remember that 5.0.0 has bumped ruby required version to 2.6.5. To install the updated development version
Hope you will appreciate. Regards |
This actually was fixed and then abandoned. Sorry. |
Having an issue with pulling the database from a WPEngine site with ssh access. The dump.sql file is created but the gzip command seems to error out. If I copy and paste the same gzip command on the remote server myself it runs fine.
movefile.yml:
If I ssh into the server and run:
it runs fine. The dump.sql file is created on the remote server and has the database data in it as well, so it really appears to be the gzip command. Not sure if there is a way for me to get a more verbose error from it some how when wordmove runs, was hoping the manually runned command would give an error I could grab to help.
Really hope I'm just doing some thing dumb other then not wanting to take up people's time for that...
The text was updated successfully, but these errors were encountered: