Hey guys,
I am not sure what's wrong and what's not anymore... A lot of the drush commands I try to execute on the remote server work, but a few don't. I know the alias is probably correctly configured because I can set variable, execute sql-queries, and rsync files folder on the remote server from local. Also I can connect without problem with an SSH key on the remote server.
I'm having the two following problems:
- The command drush @alias.remote st does not output anything in the console, when executed from local (linux).
- drush @alias.remote sql-drop hangs without showing any errors.
In both case, --debug options does not show any error or warning.
I am willing to give more info if needed, but right now I am not sure what to do to further debug that...
Comments
Comment #1
hles commentedMaybe I've not provided enough info on what's going on.
- I have a drush file called website.aliases.drushrc.php in .drush folder
Inside I have the following configuration:
- If I call
drush @website.staging st --debug, its returns me an empty line. Debug info is as follow:Question is: should it returns the actual info of the remote Drupal installation? If yes, what can be the reasons why it would return an empty line without errors?
Thank you,
Comment #2
greg.1.anderson commenteddrush @alias.remote st is working for me right now.Try taking that last line from the debug output (that is,
ssh -o PasswordAuthentication=no <host> 'drush --invoke --debug --uri=staging.<website> --root=/home/www/<website>/staging --verbose st --db-url='\''...'\'' --dump-dir=/home/www/... 2>&1' 2>&1) and execute it directly in the shell. It should work behave the same in the shell as it does from Drush. Debug by experimenting with different options, and see if you can find out what is causing the problems. From there, a more permanent solution could likely be found.Comment #3
greg.1.anderson commentedComment #4
hles commentedI tried running the command like you said and if I remove both "2>&1" from the command (and also --verbose and --debug), then I get the output I'd expect from
drush @alias.remote st.So the command is working fine, just the output is not redirected correctly ?
Comment #5
greg.1.anderson commentedThis is a problem in Drush; not sure what to suggest in the short term. Help out at #1721586: Improve Drush's handling of STDERR in backend invoke if possible.