From: kevin molcard <kev2041@gmail.com>
To: Konstantin Khomoutov <flatworm@users.sourceforge.net>
Cc: git-users@googlegroups.com, git@vger.kernel.org
Subject: Re: [git-users] Git clone fails with "bad pack header", how to get remote log
Date: Tue, 30 Oct 2012 08:01:12 +0100 [thread overview]
Message-ID: <508F7B38.5020603@gmail.com> (raw)
In-Reply-To: <20121029211854.b58c791d30a6c8d68665e574@domain007.com>
Hi Konstantin,
thanks for the reply.
The versions of git are:
- on remote: 1.5.6.5
- on windows build machine: 1.7.11.msysgit.1
- on mac build machine: 1.7.3.4
I will try to install latest git version on my remote server and get
back to you.
thanks again
Kevin
On 10/29/12 6:18 PM, Konstantin Khomoutov wrote:
> On Mon, 29 Oct 2012 09:52:54 -0700 (PDT)
> Kevin Molcard <kev2041@gmail.com> wrote:
>
>> I have a problem with my build system.
>>
>> I have a remote server with a relatively large repository (around 12
>> GB, each branch having a size of 3 GB).
>>
>> I have also 2 build servers (Mac, Windows) that are cloning the repo
>> from the remote.
>>
>> Sometimes (very often when several git clone are sent at the same
>> time), I have the following error:
>>
>> remote: internal server error
>> fatal: protocol error: bad pack header
>>
>> I know that it happens when the remote is compressing objects (thanks
>> to `--progress -v` flags) because the last line of the log before the
>> erro is:
>> remote: Compressing objects: 93% (17959/19284) [K
>>
>> * So I have 2 questions, does anybody what is the problem and what
>> should I do?
>> * Is there a way to get a more precise log from the remote to debug
>> this problem?
> This reminds me of a bug fixed in 1.7.12.1 [1]:
>
> * When "git push" triggered the automatic gc on the receiving end, a
> message from "git prune" that said it was removing cruft leaked to
> the standard output, breaking the communication protocol.
>
> In any case, bugs should be reported to the main Git list (which is
> git at vger.kernel.org), not here.
> I'm Cc'ing the main Git list so you'll get any responses from there, if
> any.
>
> Kevin, please answer to this message (keeping all the Ccs -- use "Reply
> to group" or "Reply to all" in your MUA) and describe exactly what Git
> versions on which platforms your have.
>
> 1. https://raw.github.com/git/git/master/Documentation/RelNotes/1.7.12.1.txt
>
next prev parent reply other threads:[~2012-10-30 7:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7f498800-ed38-474d-86ad-cb937be68173@googlegroups.com>
[not found] ` <7f498800-ed38-474d-86ad-cb937be68173-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2012-10-29 17:18 ` Git clone fails with "bad pack header", how to get remote log Konstantin Khomoutov
2012-10-30 7:01 ` kevin molcard [this message]
[not found] ` <20121029211854.b58c791d30a6c8d68665e574-g5ZlayWIM10NZ+ppGFcyYQ@public.gmane.org>
2012-10-30 14:57 ` kevin molcard
2012-10-31 14:19 ` [git-users] " Jeff King
[not found] ` <20121031141955.GC24291-bBVMEuqLR+SYVEpFpFwlB0AkDMvbqDRI@public.gmane.org>
2012-10-31 14:25 ` kevin molcard
2012-10-31 14:34 ` kevin molcard
2012-11-01 11:15 ` [git-users] " Jeff King
2012-11-01 15:38 ` kevin molcard
2012-10-31 14:17 ` Fwd: " kevin molcard
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=508F7B38.5020603@gmail.com \
--to=kev2041@gmail.com \
--cc=flatworm@users.sourceforge.net \
--cc=git-users@googlegroups.com \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.