* Problem while cloning a git repo
@ 2013-11-12 12:50 ycollette.nospam
2013-11-13 0:20 ` brian m. carlson
0 siblings, 1 reply; 6+ messages in thread
From: ycollette.nospam @ 2013-11-12 12:50 UTC (permalink / raw)
To: git
Hello,
When I clone a repository, I get an error from git:
git clone http://192.168.0.18:8080/test test_Gerrit
Clonage dans 'test_Gerrit'...
remote: Counting objects: 25106, done
remote: Finding sources: 100% (25106/25106)
error: RPC failed; result=56, HTTP code = 200iB | 8.12 MiB/s
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
The repo has some "big" zip files commited inside.
I use fedora 19 64 bits and git version is 1.8.3.1.
Best regards,
YC
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem while cloning a git repo
2013-11-12 12:50 Problem while cloning a git repo ycollette.nospam
@ 2013-11-13 0:20 ` brian m. carlson
2013-11-13 7:58 ` Yann COLLETTE
[not found] ` <52832DA0.7040108@free.fr>
0 siblings, 2 replies; 6+ messages in thread
From: brian m. carlson @ 2013-11-13 0:20 UTC (permalink / raw)
To: ycollette.nospam; +Cc: git
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On Tue, Nov 12, 2013 at 01:50:24PM +0100, ycollette.nospam@free.fr wrote:
> Hello,
>
> When I clone a repository, I get an error from git:
>
> git clone http://192.168.0.18:8080/test test_Gerrit
> Clonage dans 'test_Gerrit'...
> remote: Counting objects: 25106, done
> remote: Finding sources: 100% (25106/25106)
> error: RPC failed; result=56, HTTP code = 200iB | 8.12 MiB/s
curl code 56 is a receive error (CURLE_RECV_ERROR). It sounds like
you're encountering some sort of network error or broken proxy. Does
cloning this repository over the git protocol or SSH work, or can you
try it over https (to avoid the proxy)?
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem while cloning a git repo
2013-11-13 0:20 ` brian m. carlson
@ 2013-11-13 7:58 ` Yann COLLETTE
[not found] ` <52832DA0.7040108@free.fr>
1 sibling, 0 replies; 6+ messages in thread
From: Yann COLLETTE @ 2013-11-13 7:58 UTC (permalink / raw)
Cc: git
Hello,
When I perform the git clone via git, it works. The problem is only
happening via http.
I tried to play with http.postBuffer and I set this parameter to it's
maximum (a little bit before a git clone triggered a memory alloc
problem) and I see that something big is trying to be downloaded. But I
don't see such a big file in my history of commits. The maximum one
seems to be around 50 Mo ...
Le 13/11/2013 01:20, brian m. carlson a écrit :
> On Tue, Nov 12, 2013 at 01:50:24PM +0100, ycollette.nospam@free.fr wrote:
>> Hello,
>>
>> When I clone a repository, I get an error from git:
>>
>> git clone http://192.168.0.18:8080/test test_Gerrit
>> Clonage dans 'test_Gerrit'...
>> remote: Counting objects: 25106, done
>> remote: Finding sources: 100% (25106/25106)
>> error: RPC failed; result=56, HTTP code = 200iB | 8.12 MiB/s
> curl code 56 is a receive error (CURLE_RECV_ERROR). It sounds like
> you're encountering some sort of network error or broken proxy. Does
> cloning this repository over the git protocol or SSH work, or can you
> try it over https (to avoid the proxy)?
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem while cloning a git repo
[not found] ` <52832DA0.7040108@free.fr>
@ 2013-11-13 23:40 ` brian m. carlson
2013-11-14 8:20 ` Yann COLLETTE
0 siblings, 1 reply; 6+ messages in thread
From: brian m. carlson @ 2013-11-13 23:40 UTC (permalink / raw)
To: Yann COLLETTE, git
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
On Wed, Nov 13, 2013 at 08:43:28AM +0100, Yann COLLETTE wrote:
> Hello,
>
> When I perform the git clone via git, it works. The problem is only
> happening via http.
> I tried to play with http.postBuffer and I set this parameter to
> it's maximum (a little bit before a git clone triggered a memory
> alloc problem) and I see that something big is trying to be
> downloaded. But I don't see such a big file in my history of
> commits. The maximum one seems to be around 50 Mo ...
Please keep the list in CC.
http.postBuffer doesn't affect clones, only pushes, so that isn't
relevant here. You're experiencing something that is dropping the
connection over HTTP. So you either have a bad proxy, or something else
is causing the connection to be dropped. Since it's only over HTTP, I
suspect it's the former.
Do you have HTTPS, and if so, does it work if you try to clone over
that?
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem while cloning a git repo
2013-11-13 23:40 ` brian m. carlson
@ 2013-11-14 8:20 ` Yann COLLETTE
2013-11-18 7:31 ` ycollette.nospam
0 siblings, 1 reply; 6+ messages in thread
From: Yann COLLETTE @ 2013-11-14 8:20 UTC (permalink / raw)
To: git
I am not able to clone via https because gerrit doesn't propose this way
of cloning.
When I clone via http, I see that git is starting the download of objects:
remote: Counting objects: 256, done
remote: Finding sources: 100% (256/256)
Receiving objects: 46% ... (this part always fails at 46 %).
So, I think that the proxy part is not a problem (there is no proxy set
here).
If I set GIT_CURL_VERBOSE=1 before cloning, I've got the following error:
* Problem (2) in the Chunked-Encoded data
* Closing connection 1
YC
Le 14/11/2013 00:40, brian m. carlson a écrit :
> On Wed, Nov 13, 2013 at 08:43:28AM +0100, Yann COLLETTE wrote:
>> Hello,
>>
>> When I perform the git clone via git, it works. The problem is only
>> happening via http.
>> I tried to play with http.postBuffer and I set this parameter to
>> it's maximum (a little bit before a git clone triggered a memory
>> alloc problem) and I see that something big is trying to be
>> downloaded. But I don't see such a big file in my history of
>> commits. The maximum one seems to be around 50 Mo ...
> Please keep the list in CC.
>
> http.postBuffer doesn't affect clones, only pushes, so that isn't
> relevant here. You're experiencing something that is dropping the
> connection over HTTP. So you either have a bad proxy, or something else
> is causing the connection to be dropped. Since it's only over HTTP, I
> suspect it's the former.
>
> Do you have HTTPS, and if so, does it work if you try to clone over
> that?
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Problem while cloning a git repo
2013-11-14 8:20 ` Yann COLLETTE
@ 2013-11-18 7:31 ` ycollette.nospam
0 siblings, 0 replies; 6+ messages in thread
From: ycollette.nospam @ 2013-11-18 7:31 UTC (permalink / raw)
To: git
When I clone a git repo from github (via https), I've no problems.
It looks like that the problem is only related to my "special" repo with big zip commited inside.
YC
----- Mail original -----
De: "Yann COLLETTE" <ycollette.nospam@free.fr>
À: git@vger.kernel.org
Envoyé: Jeudi 14 Novembre 2013 09:20:51
Objet: Re: Problem while cloning a git repo
I am not able to clone via https because gerrit doesn't propose this way
of cloning.
When I clone via http, I see that git is starting the download of objects:
remote: Counting objects: 256, done
remote: Finding sources: 100% (256/256)
Receiving objects: 46% ... (this part always fails at 46 %).
So, I think that the proxy part is not a problem (there is no proxy set
here).
If I set GIT_CURL_VERBOSE=1 before cloning, I've got the following error:
* Problem (2) in the Chunked-Encoded data
* Closing connection 1
YC
Le 14/11/2013 00:40, brian m. carlson a écrit :
> On Wed, Nov 13, 2013 at 08:43:28AM +0100, Yann COLLETTE wrote:
>> Hello,
>>
>> When I perform the git clone via git, it works. The problem is only
>> happening via http.
>> I tried to play with http.postBuffer and I set this parameter to
>> it's maximum (a little bit before a git clone triggered a memory
>> alloc problem) and I see that something big is trying to be
>> downloaded. But I don't see such a big file in my history of
>> commits. The maximum one seems to be around 50 Mo ...
> Please keep the list in CC.
>
> http.postBuffer doesn't affect clones, only pushes, so that isn't
> relevant here. You're experiencing something that is dropping the
> connection over HTTP. So you either have a bad proxy, or something else
> is causing the connection to be dropped. Since it's only over HTTP, I
> suspect it's the former.
>
> Do you have HTTPS, and if so, does it work if you try to clone over
> that?
>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-11-18 7:32 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-11-12 12:50 Problem while cloning a git repo ycollette.nospam
2013-11-13 0:20 ` brian m. carlson
2013-11-13 7:58 ` Yann COLLETTE
[not found] ` <52832DA0.7040108@free.fr>
2013-11-13 23:40 ` brian m. carlson
2013-11-14 8:20 ` Yann COLLETTE
2013-11-18 7:31 ` ycollette.nospam
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 NNTP newsgroup(s).