search

mitchellh / vagrant-aws

Use Vagrant to manage your EC2 and VPC instances.
MIT License
2.61k stars 572 forks source link

Rsync Issue #379

Open pete-hodgman opened 9 years ago

pete-hodgman commented 9 years ago

I am not sure what is causing this. Its not clear if it is something I have configured incorrectly in Vagrant or something else. I intermittently get an rsync error when using Vagrant to rsync files to an AWS EC2 host. Please see the error below. It does not happen always but it does happen from time to time.

There was an error when attempting to rsync a synced folder. Please inspect the error message below for more info.

Host path: /Users/pete/dev/inv/ba/XOSPassport/scripts/ Guest path: /bimassure/XOSPassport/scripts Command: rsync --verbose --archive --delete -z --copy-links --no-owner --no-group --rsync-path sudo rsync -e ssh -p 22 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i '/Users/pete/dev/devops/vagrant/awstest/vagkey.pem' --exclude .vagrant/ /Users/pete/dev/inv/ba/XOSPassport/scripts/ ubuntu@54.227.251.229:/bimassure/XOSPassport/scripts Error: Connection closed by 54.227.251.229 rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at /SourceCache/rsync/rsync-45/rsync/io.c(453) [sender=2.6.9]

pete-hodgman commented 9 years ago

A full debug gist can be found here..

https://gist.github.com/pete-hodgman/742032ae015bb497dcfb

kenorb commented 7 years ago

Try adding:

config.ssh.pty = true

into your Vagrantfile.

Related: mitchellh/vagrant/issues/6780