alessandro-fazzi
commented
2 years ago Hi @ThinkByDesign ,
thanks for the inquiry. As a first try I'd suggest to try to add a config to your ~/.ssh/config (if I understood you already have one so you know what I'm talking about) under the interested host:
Host example.com
ControlMaster auto
ControlPath /tmp/master-%r@%h:%p
Compression yesI know that with some hosting there are problem with SSH auth during db transfer operations. This is due to wordmove making a lot of different close and subsequent connections. Some hosting providers have something like anti-burst security config conflicting with this behaviour.
Having that configurations you'd end having something like a socket open for all the connections.
I'm not sure it will work because its also possible that every connection will open the "socket", do its business then release the "socket" and pass on to the next operation. But it worth a try.
In the past I've tried to solve this problem by code here https://github.com/welaika/wordmove/issues/528 but never received enough feedback and never had the opportunity to test it myself; so I don't know if my "blind coding" made something interesting there.
ThinkByDesign
humblecoder
So, to be clear, I'm new at wordmove. This is my second site with it, and the first one isn't quite working yet, but for different reasons.
Describe the bug
When wordmove gets to the remote dump stage, it generates the error noted below (SSH authentication). What's confusing is that it's just successfully conducted SSH connections to move all the files successfully. I'm also able to ssh directly from the command line, as well as through FileZilla.
When I login to the web server and look at the wp-content directory, I don't see a dump file there. HOWEVER, if I login to the web server (using the credential in the config file) and just run the mysqldump (substituting real values for the secrets omitted in the error), it works, and generates the dump.sql file.
I've also looked at the auth.log for possible clues. When I do a push with --all, I see several chunks like this: Oct 6 02:22:16 web02 sshd[8898]: Accepted publickey for [correct user] from 99.164.33.88 port 57945 ssh2: [key stuff] Oct 6 02:22:16 web02 sshd[8898]: pam_unix(sshd:session): session opened for user [correct user] by ([correct uid]) Oct 6 02:22:16 web02 systemd-logind[1422]: New session 82907 of user [correct user]. Oct 6 02:22:17 web02 sshd[8974]: Received disconnect from 99.164.33.88 port 57945:11: disconnected by user Oct 6 02:22:17 web02 sshd[8974]: Disconnected from user [correct user] 99.164.33.88 port 57945 Oct 6 02:22:17 web02 sshd[8898]: pam_unix(sshd:session): session closed for user [correct user] Oct 6 02:22:17 web02 systemd-logind[1422]: Removed session 82907.
but then when it tries to do the database thing, it just gets this: Oct 6 02:22:22 web02 sshd[9364]: Connection closed by authenticating user [correct user - same as above] 99.164.33.88 port 57981 [preauth]
It's almost like it's using different credentials for that step? I do have my ssh config setup to filter by user and apply different keys (I have two logins to the same server with their own keys - both work correctly from the command line, but maybe this code is doing something different?)
Any help would be appreciated!!
Wordmove command wordmove push -e staging -all
Expected behavior Pushing all the files up to the remote staging server (which succeeded). Pushing database up to the remote server (failed).
movefile.yml
Exception/trace
Environment (please complete the following information):
Doctor Reports all green except for ❌ error | [/database/mysql_options] key 'mysql_options:' is undefined.