public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: overseers@sourceware.org
Subject: rsync woes
Date: Sun, 19 Jul 2015 10:27:00 -0000	[thread overview]
Message-ID: <20150719102727.GG3864@calimero.vinschen.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]

Hi overseers,


we're running a couple of local mirrors @ home.  One of them is a mirror
for the Cygwin distro.

Rsync is usually started via cron at 8 or 9 pm UTC, depending on DST,
so it's running over night our time.

This worked fine for many years, but for some weeks now, rsync'ing the
cygwin distro packages fails every single day.

The strange thing is, this seems to depend on the time of day.  If I
start rsync manually at other times of the day, say, in the morning
9am UTC, it runs fine.  However, running it manually later in the day
it's growing more likely to fail.

The rsync error message looks like this:

$ rsync -avhz --stats --progress --filter=dir-merge_/.rsync_filter --delete-delay
--delete-excluded -K cygwin.com::cygwin-ftp .
[...]
inflate returned -3 (227 bytes)
rsync error: error in rsync protocol data stream (code 12) at token.c(557)
[receiver=3.1.1]
rsync: connection unexpectedly closed (45130 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(235)
[generator=3.1.1]


Do you have an idea what the problem could be here and how to avoid it?


Thanks,
Corinna

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2015-07-19 10:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-19 10:27 Corinna Vinschen [this message]
2015-08-03  7:56 ` 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=20150719102727.GG3864@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=overseers@sourceware.org \
    /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).