-
Notifications
You must be signed in to change notification settings - Fork 51
Drush launcher fails sql-sync after upgrade from 0.5.1 -> 0.6.0 #60
Comments
Tagging @schady4 |
I see the same:
|
@weitzman Do you have any idea whats causing this? @ixisandyr @schady4 @dougmorin Could you add the --debug oder --verbose flag to the drush commands and post the full error log? Its hard to tell what is going on from the current error reports. Thanks! |
Hi, here's the comparison between 0.6.0 and 0.5.1 where drush launcher is installed at /usr/local/bin/drush on the sql-sync target - (alias @portal.xxxxx.vm7) 0.6.0
0.5.1
|
I usually don't use the Drush launcher, but I ran into this recently when targeting a remote system I didn't set up. When sql-sync passed through the Drush Launcher on the remote system, the I worked around the problem by adding a |
We switched from system to proc_open in 0.6.x. #44 I always setup the proper drush-script path in my site aliases. Makes debugging easier and it removes the requirement to have a globally installer drush on the remote system. |
@webflo This issue seems to suggest not setting This work around did help though |
Note that there's also a bug in Drush sql-sync when mixing Drush 9.6.x with Drush 9.5.x and earlier. Unrelated to this problem, but thought I'd mention it in case people run into that problem while working on this one. |
This was working before, but the sql-sync now fails after the upgrade. Looking for advice and to see if anybody else has seen this issue?
The text was updated successfully, but these errors were encountered: