From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: rsync fails on Win 2012 server [was: [ANNOUNCEMENT] Cygwin 3.0.1-1]
Date: Sun, 03 Mar 2019 01:19:00 -0000 [thread overview]
Message-ID: <a7fb78f1-93a1-3f09-be95-c7cfd001ea7e@redhat.com> (raw)
In-Reply-To: <announce.20190220115920.GQ4256@calimero.vinschen.de>
On 2/20/19 5:59 AM, Corinna Vinschen wrote:
> Hi folks,
>
>
> I uploaded a new Cygwin release 3.0.1-1.
>
> THis is mainly a bugfix release.
This version is failing for me on Windows Server 2012. In fact, I
bisected it; snapshot 20190126 works, 20190127 and later fail in the
same manner, including 20190302. Failures look like this (here from
32-bit, where uname reports CYGWIN_NT-6.2-WOW, but 64-bit sees the same):
$ cygport coreutils.cygport prep
...
>>> Preparing working source directory
8 [main] rsync 2980 fixup_mmaps_after_fork: VirtualQueryEx failed
for MAP_PRIVATE address 0xFFE60000, Win32 error 5
2084 [main] rsync 2980 C:\cygwin\bin\rsync.exe: *** fatal error in
forked process - recreate_mmaps_after_fork_failed
2482 [main] rsync 2980 cygwin_exception::open_stackdumpfile: Dumping
stack trace to rsync.exe.stackdump
9 [main] rsync 652 fork: child -1 - forked process 2980 died
unexpectedly, retry 0, exit code 0x100, errno 11
rsync: fork failed in do_recv: Resource temporarily unavailable (11)
rsync error: error in IPC code (code 14) at main.c(897) [Receiver=3.1.2]
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-03-03 1:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 16:28 [ANNOUNCEMENT] Cygwin 3.0.1-1 Corinna Vinschen
2019-03-03 1:19 ` Eric Blake [this message]
2019-03-03 11:43 ` rsync fails on Win 2012 server [was: [ANNOUNCEMENT] Cygwin 3.0.1-1] Corinna Vinschen
2019-03-04 17:50 ` Eric Blake
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a7fb78f1-93a1-3f09-be95-c7cfd001ea7e@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).