public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Frank Fesevur <ffes@users.sourceforge.net>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: rsyncd broken
Date: Fri, 22 Aug 2014 12:43:00 -0000	[thread overview]
Message-ID: <CAKf2h5QUACgams++7Vm9N2uCP63hY2m5wvEDhe_odeSioSA-fg@mail.gmail.com> (raw)

Jari,

As I reported earlier rsync 3.1.0 is broken on cygwin.
http://www.cygwin.com/ml/cygwin/2014-06/msg00212.html
http://www.cygwin.com/ml/cygwin/2014-06/msg00442.html

Any news on that issue yet?

We run cygwin rsync daemons on our Windows servers and have a remote
Ubuntu server that backups the important data using rsnapshot. Earlier
this week I accidentally upgraded from 3.0.9 to your 3.1.0 on one of
our servers and that night the backup failed with these (client side)
error.

@ERROR: setuid 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.202.230/backup-d/DataWeb/
@ERROR: setuid 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.202.230/backup-d/wwwroot/

I reverted to 3.0.9 and it works as expected again.

But these error don't seem to be related to the 3.1.0 performance
issues, so do you have any idea why it fails? Could the additional
debian patch you've added cause this?

I will try a self build vanilla rsync.exe 3.1.1 this weekend or early
next week and see how that works.

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

             reply	other threads:[~2014-08-22 12:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 12:43 Frank Fesevur [this message]
2014-08-22 16:17 ` Yaakov Selkowitz
2014-11-06 17:51   ` Marco Atzeri
2014-08-25  7:47 ` Frank Fesevur
2014-08-28  8:22   ` Frank Fesevur
2014-08-28 10:06     ` Corinna Vinschen

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=CAKf2h5QUACgams++7Vm9N2uCP63hY2m5wvEDhe_odeSioSA-fg@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).