From: Jim Meyering <jim@meyering.net>
To: ppluzhnikov@google.com (Paul Pluzhnikov)
Cc: overseers@sourceware.org
Subject: Re: git://sourceware.org/git/glibc.git is having trouble?
Date: Sun, 04 Mar 2012 19:14:00 -0000 [thread overview]
Message-ID: <87eht89o24.fsf@rho.meyering.net> (raw)
In-Reply-To: <20120304184833.79D6D19096D@elbrus2.mtv.corp.google.com> (Paul Pluzhnikov's message of "Sun, 4 Mar 2012 10:48:33 -0800 (PST)")
Paul Pluzhnikov wrote:
> Greetings,
>
> I am having repeated (but intermittent) problems pulling from
> git://sourceware.org/git/glibc.git:
>
> $ git pull
> fatal: read error: Connection reset by peer
> $ git pull
> fatal: read error: Connection reset by peer
> $ git pull
> fatal: read error: Connection reset by peer
> $ git pull
> fatal: read error: Connection reset by peer
> $ git pull
> fatal: read error: Connection reset by peer
> ...
> $ git pull
> remote: Counting objects: 201, done.
> remote: Compressing objects: 100% (89/89), done.
> remote: Total 124 (delta 52), reused 104 (delta 33)
> Receiving objects: 100% (124/124), 138.82 KiB | 261 KiB/s, done.
>
> $ git pull
> Already up-to-date.
>
>
> This is happening at
> Sun Mar 4 10:47:50 PST 2012
>
> I also had similar trouble last Friday.
I heard that due to recent DoS problems, someone imposed a new
limit on maximum number of connections. I have heard that this
probably caused Tom Tromey to see the same sort of failure.
This makes me think that the limit is still too low.
However, I've just tried to update my own glibc clone
Sun Mar 4 20:12:13 CET 2012
and it succeeded.
next prev parent reply other threads:[~2012-03-04 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 18:48 Paul Pluzhnikov
2012-03-04 19:14 ` Jim Meyering [this message]
2012-03-04 19:36 ` Frank Ch. Eigler
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=87eht89o24.fsf@rho.meyering.net \
--to=jim@meyering.net \
--cc=overseers@sourceware.org \
--cc=ppluzhnikov@google.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).