From: Frank Fesevur <ffes@users.sourceforge.net>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: rsync still broken
Date: Thu, 12 Mar 2015 11:28:00 -0000 [thread overview]
Message-ID: <CAKf2h5TzBP7KYO+NhZ7oVRpb-O_q86RvFxa1NacVWgRVu8BfRA@mail.gmail.com> (raw)
Hi Jari,
It looks like rsync is still broken. When you released 3.1.0 it had an
upstream bug that made it extremely slow on cygwin. Other then that it
also had another problem that I reported here:
https://www.cygwin.com/ml/cygwin/2014-08/msg00440.html
Yaakov made 3.1.0 test and we all automatically reverted to 3.0.9.
Recently 3.1.1 was released leaving the broken test version 3.1.0 as
previous. I didn't update my servers yet, The day before yesterday I
did, so I went from 3.0.9 to 3.1.1.
And yesterday I saw that my backup *completely* failed because of these errors:
@ERROR: setgid failed
rsync error: error starting client-server protocol (code 5) at
main.c(1653) [Receiver=3.1.0]
ERROR: /usr/bin/rsync returned 5 while processing
rsync://192.168.200.208/backup-d/DataShares/
@ERROR: setgid failed
rsync error: error starting client-server protocol (code 5) at
main.c(1653) [Receiver=3.1.0]
ERROR: /usr/bin/rsync returned 5 while processing
rsync://192.168.200.208/backup-d/DataGit/
@ERROR: setgid failed
Very similar error as I reported for 3.1.0.
FYI, I run the cygwin based rsync daemon on my Windows servers and
have a Ubuntu server that backups the data with rsnapshot (which
utilizes rsync to do the transfers). The errors above are shown on the
Ubuntu server.
Luckily I still had a 3.0.9 executable on one machine and I've put
that exe on all the updated servers to make sure the backup worked
again last night. So those systems new think they have 3.1.1 but the
actually have the exe of good old properly working 3.0.9
Note that 3.0.9 is not available on the mirrors anymore. I hope that
it can be restored on the mirrors and made current again for the time
being and that this you have time to look into this problem. But the
bottom line is that 3.1.x breaks my backup.
Regards,
Frank
--
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 reply other threads:[~2015-03-12 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 11:28 Frank Fesevur [this message]
2015-03-12 23:50 ` Linda Walsh
2015-03-13 11:20 ` Frank Fesevur
2015-03-20 9:15 ` Linda Walsh
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=CAKf2h5TzBP7KYO+NhZ7oVRpb-O_q86RvFxa1NacVWgRVu8BfRA@mail.gmail.com \
--to=ffes@users.sourceforge.net \
--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).