Vagrant rsync (from cygwin) on windows 10 has a fork memory error

I had a rather annoying problem with roaming rsync on my new installed Windows 10 64-bit laptop.

> There was an error when attempting to rsync a synced folder. Please
> inspect the error message below for more info.
> 
> Host path: /c/Users/kryst/Projects/OSTSped/ostsped/ Guest path:
> /vagrant Command: rsync --verbose --archive --delete -z --copy-links
> --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o ControlMaster=auto -o
> ControlPath=C:/Users/kryst/AppData/Local/Temp/ssh.952 -o
> ControlPersist=10m -o StrictHostKeyChecking=no -o IdentitiesOnly=true
> -o UserKnownHostsFile=/dev/null -i 'C:/Users/kryst/Projects/OSTSped/ostsped/.vagrant/machines/default/virtualbox/private_key'
> --exclude .vagrant/ /c/Users/kryst/Projects/OSTSped/ostsped/ vagrant@127.0.0.1:/vagrant Error:       0 [main] rsync 1228
> C:\cygwin64\bin\rsync.EXE: *** fatal error in forked process - fork:
> can't reserve memory for parent stack 0x600000 - 0x800000, (child has
> 0x400000 - 0x600000), Win32 error 487    2512 [main] rsync 1228
> cygwin_exception::open_stackdumpfile: Dumping stack trace to
> rsync.EXE.stackdump
>       1 [main] rsync 4736 fork: child -1 - forked process 1228 died unexpectedly, retry 0, exit code 0x100, errno 11 rsync: fork: Resource
> temporarily unavailable (11) rsync error: error in IPC code (code 14)
> at pipe.c(65) [sender=3.1.1]

I am looking for an answer for a few days. I tried using 32 and 64 bit versions of cygwin, powershell, git bash. I tried updating the cygwin prefix in / cygdrive, / or even in the home directory (C: \ User \ kryst). I tried to reinstall.

Nothing solved the problem.

Actual versions of softwere:

Vagrant 1.8.1

Cygwin64 setup.exe version 2.873 (64-bit)

Rsync 3.1.1-1

OpenSSH 7.1p1-1

+4
source share
3 answers

The newer version of rsync seems to work fine

  • Vagrant 1.8.5
  • rsync 3.1.2
0

: , 32- rsync - , .

-

Vagrant, 64- cygwin rsync 32- .

: https://cygwin.com/ml/cygwin/2013-07/msg00720.html

, , .

+1

Try the workaround discussed here.

https://github.com/mitchellh/vagrant/issues/3230

-2
source

Source: https://habr.com/ru/post/1622473/


All Articles