Skip to content
This repository has been archived by the owner on Feb 11, 2022. It is now read-only.

Rsync Issue #379

Open
pete-hodgman opened this issue Apr 1, 2015 · 2 comments
Open

Rsync Issue #379

pete-hodgman opened this issue Apr 1, 2015 · 2 comments

Comments

@pete-hodgman
Copy link

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
Copy link
Author

A full debug gist can be found here..

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

@kenorb
Copy link

kenorb commented Dec 2, 2016

Try adding:

config.ssh.pty = true

into your Vagrantfile.

Related: hashicorp/vagrant/issues/6780

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants