2

Since I upgraded drush 5.10 -> 7.0-dev today, sql-sync fails to work with my existing alias file.

Using the command drush sql-sync @limelive @limedev fails.

The %dump-dir paths on both local and remote aliases correctly address existing directories. --debug shows the remote sql dump success:

 Database dump saved to /home/aegir/drush-backups/limetreethornfor/20140411235252/limetreethornfor_20140411_235252.sql.gz 

but later reports

rsync: link_stat "/var/aegir/platforms/aventura-2014-04-11-1/Array" failed: No such file or directory  

This suggest new command syntax incorrectly diagnosed. What am I doing wrong?

closed as off-topic by Pierre.Vriens, Shawn Conn, Adrian Cid Almaguer, kenorb, No Sssweat Jul 25 '16 at 10:10

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This question was caused by a problem that can no longer be reproduced, was solved by a cache clear, or was a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers." – Pierre.Vriens, Shawn Conn, Adrian Cid Almaguer, kenorb, No Sssweat
If this question can be reworded to fit the rules in the help center, please edit the question.

  • I have found that Drush 7 is fine now - as long as you have the same version installed on both local and remote systems. – iainH Aug 28 '15 at 13:55
2

This is a bug in Drush master. Please put an issue in the queue on Github.

1

The bug has been reported here.

I used this workaround (dump remote db and import it to local db):

drush @example.prod sql-dump > /tmp/example.sql
drush sql-drop -y
drush sql-query --file=/tmp/example.sql
drush cc all
0

This is still a bug for me even in the Drush 7 stable release. I had to go back to Drush 6.6 and it works fine.

  • I have found that Drush 7 is fine - as long as you have the same version installed on both local and remote systems. – iainH Aug 28 '15 at 13:55

Not the answer you're looking for? Browse other questions tagged or ask your own question.