public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Spurious "Connection reset by peer" problems anybody?
Date: Mon, 21 Feb 2011 15:06:00 -0000	[thread overview]
Message-ID: <20110221150636.GF17868@calimero.vinschen.de> (raw)
In-Reply-To: <4D627C96.8000807@cornell.edu>

On Feb 21 09:54, Ken Brown wrote:
> On 2/21/2011 9:26 AM, Corinna Vinschen wrote:
> >On Feb 21 15:01, Corinna Vinschen wrote:
> >>I spoke too soon. [...]
> >
> >Er... btw., is the situation something which is local to your
> >environment or is it something which can be easily reproduced?
> 
> The short answer is that it wouldn't be easy.  Here are the details:
> 
> I keep a local mirror of the emacs bzr repository.  I connect to the
> repository via bzr+ssh.  Every few days I refresh my mirror with
> 'bzr up'.  When I do this from work, where I have a fast ethernet
> connection, there's no problem.  When I do it from home, where I
> connect to the internet via a wireless router, it often fails with
> the "Software caused connection abort" message.  I keep retrying and
> eventually it works. Sometimes it takes 10 tries, other times it
> works on the first try.
> 
> I've had similar problems in the past when using rsync to maintain a
> local mirror of the texlive repository.  In that case I think the
> error message was always "Connection reset by peer".  Once again,
> the problem only occurred when working from home.
> 
> I've always assumed that there was some issue with my home network
> setup or my ISP, but I had no idea how to track it down.  It never
> occurred to me that it could be a Cygwin/Windows problem.

The problem is that this is not necessarily a Cygwin/Windows problem.
It's just possible that Windows plays a role here.

As far as this problem goes, it would only occur at the end of a
connection, when close() is called on the socket on the Windows side.
The error message would occur on the peer side, independent of the OS
it's running on.  If the connection just breaks at some arbitary point,
it's almost surely not the problem I'm talking about.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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:[~2011-02-21 15:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 10:44 Corinna Vinschen
2011-02-21 13:49 ` Ken Brown
2011-02-21 14:02   ` Corinna Vinschen
2011-02-21 14:26     ` Corinna Vinschen
2011-02-21 14:54       ` Ken Brown
2011-02-21 15:06         ` Corinna Vinschen [this message]
2011-02-21 15:27           ` Ken Brown
2011-02-21 15:34             ` Corinna Vinschen
2011-02-21 22:08               ` Ken Brown
2011-02-22  8:55                 ` Corinna Vinschen
     [not found] ` <AANLkTimoBKaVBj9yOvLJunrtEV0tY+ruJG2bHV7moc9q@mail.gmail.com>
2011-02-22 15:40   ` Mirko Vukovic
2011-02-22 15:55     ` Corinna Vinschen
2011-02-22 16:14 lynn
2011-03-22 23:27 MS

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=20110221150636.GF17868@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.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).