Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rsync` failed on Vagrant 1.8.6 #7908

Closed
omps opened this issue Oct 18, 2016 · 5 comments
Closed

rsync` failed on Vagrant 1.8.6 #7908

omps opened this issue Oct 18, 2016 · 5 comments

Comments

@omps
Copy link

omps commented Oct 18, 2016

Vagrant version

~$ vagrant --version
Vagrant 1.8.6

Host operating system

~$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.5 (Santiago)

Guest operating system

Centos 7

Vagrantfile

Vagrant.configure("2") do |config|
  config.hostmanager.enabled = true
  config.hostmanager.ignore_private_ip = false
  config.hostmanager.include_offline = true

  config.vm.define "devopsmain" do |devopsmain|
    devopsmain.vm.box  = "centos/7"
    devopsmain.vm.hostname = "devopsmain"
    devopsmain.vm.network :private_network, ip: "192.168.250.100"
    devopsmain.hostmanager.alias = %w(devopsmain)
    devopsmain.vm.provider :virtualbox do |vb|
      vb.customize ["modifyvm", :id, "--memory", "4096"]
      vb.customize ["modifyvm", :id, "--cpus", "2"]
    end
    devopsmain.vm.provision "shell", inline: <<-SHELL
       sudo yum update -y
       sudo rpm -ivh https://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
       sudo yum install puppetserver -y
       sudo sed -i 's/2g/512m/g' /etc/sysconfig/puppetserver
    SHELL
  end

Actual behavior

==> devopsmain: Rsyncing folder: /home/singho/devopsenv/ => /home/vagrant/sync
There was an error when attempting to rsync a synced folder.
Please inspect the error message below for more info.

Host path: /home/singho/devopsenv/
Guest path: /home/vagrant/sync
Command: "rsync" "--verbose" "--archive" "--delete" "-z" "--copy-links" "--no-owner" "--no-group" "--rsync-path" "sudo rsync" "-e" "ssh -p 2200 -o LogLevel=FATAL -o ControlMaster=auto -o ControlPath=/tmp/ssh.849 -o ControlPersist=10m -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i '/home/singho/devopsenv/.vagrant/machines/devopsmain/virtualbox/private_key'" "--exclude" ".vagrant/" "/home/singho/devopsenv/" "vagrant@127.0.0.1:/home/vagrant/sync"
Error: command-line: line 0: Bad configuration option: ControlPersist
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(600) [sender=3.0.6]

References

#6702

Issue 1:

As per the issue #6702 I removed the following lines

         unless Vagrant::Util::Platform.windows?
           controlpath = File.join(Dir.tmpdir, "ssh.#{rand(1000)}")
           control_options = "-o ControlMaster=auto -o ControlPath=#{controlpath} -o ControlPersist=10m "
         end

which solves the issue.

I am wondering why my system is being detected as a windows machine by vagrant?

@keomabrun
Copy link

I have the same problem with the same OS and Vagrant v1.9.7.
This solution did not work for me.

Rsync version: 3.0.6
OpenSSH: version 5.3
Virtualbox version: 5.0.20

@snfnwgi
Copy link

snfnwgi commented Sep 30, 2017

Who can answer my question
#9010

@vhosakot
Copy link

When I did vagrant up with the box centos/7 (virtualbox, 1703.01), ==> default: Rsyncing folder: /root/ => /vagrant was stuck for me too, and adding
config.vm.synced_folder '.', '/vagrant', disabled: true
in Vagrantfile resolved the issue for me and rsync did not happen.

@chrisroberts
Copy link
Member

Hi there,

It looks like this has been resolved within a previously shipped version of Vagrant so I am now closing this issue. If the original issue was not fully resolved, please reopen this issue or create a new one.

Cheers!

@ghost
Copy link

ghost commented Mar 28, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Mar 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants