threads / discuss / 10747

git push failing, unpacker error

Subject: git push failing, unpacker error

## tl;dr

6 messages between Nov 9, 2007 and Nov 9, 2007.

replies: 5people: 3as markdown or json

Jon Smirl· Nov 9, 2007, 05:55 UTC · lore

Why is this push failing?

jonsmirl@terra:~/mpc5200b$ git push dreamhost
updating 'refs/remotes/linus/m24' using 'refs/heads/m24'
  from 0000000000000000000000000000000000000000
  to   06c52341cc9265b23e2d11eb631ff45e763215c0
updating 'refs/remotes/linus/m25' using 'refs/heads/m25'
  from 0000000000000000000000000000000000000000
  to   bef47d2064dd1a848597246291ef8a7654387dde
updating 'refs/remotes/linus/m26' using 'refs/heads/m26'
  from 0000000000000000000000000000000000000000
  to   35200c360d85fb74da55e57dfb16cb9d50b253e9
updating 'refs/remotes/linus/m28' using 'refs/heads/m28'
  from 0000000000000000000000000000000000000000
  to   a77cec0752aa8a00b95a44d1028d5f9b989354a4
updating 'refs/remotes/linus/m29' using 'refs/heads/m29'
  from 0000000000000000000000000000000000000000
  to   0c4bfa1cbed0070e5d0cc739ab0ac4c04290b8d3
Counting objects: 81156, done.
Compressing objects: 100% (16575/16575), done.
Writing objects: 100% (70133/70133), done.
Total 70133 (delta 57185), reused 66194 (delta 53490)
unpack index-pack abnormal exit
ng refs/remotes/linus/m24 n/a (unpacker error)
ng refs/remotes/linus/m25 n/a (unpacker error)
ng refs/remotes/linus/m26 n/a (unpacker error)
ng refs/remotes/linus/m28 n/a (unpacker error)
ng refs/remotes/linus/m29 n/a (unpacker error)
error: failed to push to 'ssh://jonsmirl1@git.digispeaker.com/~/mpc5200b.git'
jonsmirl@terra:~/mpc5200b$

-- 
Jon Smirl
jonsmirl@gmail.com

Jon Smirl· Nov 9, 2007, 14:37 UTC · re: Jon Smirl · lore

Re: git push failing, unpacker error

I updated both sides to current git and it still fails. How do I debug this? What's causing this, "error: pack-objects died with strange error"?

jonsmirl@terra:~/mpc5200b$ git push dreamhost
To ssh://jonsmirl1@git.digispeaker.com/~/mpc5200b.git
 * [new branch]      m24 -> linus/m24
 * [new branch]      m25 -> linus/m25
 * [new branch]      m26 -> linus/m26
 * [new branch]      m28 -> linus/m28
 * [new branch]      m29 -> linus/m29
Counting objects: 81156, done.
Compressing objects: 100% (15280/15280), done.
error: pack-objects died with strange errorMiB | 412 KiB/s
unpack index-pack abnormal exit
ng refs/remotes/linus/m24 n/a (unpacker error)
ng refs/remotes/linus/m25 n/a (unpacker error)
ng refs/remotes/linus/m26 n/a (unpacker error)
ng refs/remotes/linus/m28 n/a (unpacker error)
ng refs/remotes/linus/m29 n/a (unpacker error)
error: failed to push to 'ssh://jonsmirl1@git.digispeaker.com/~/mpc5200b.git'
jonsmirl@terra:~/mpc5200b$

-- 
Jon Smirl
jonsmirl@gmail.com

Jon Smirl· Nov 9, 2007, 14:43 UTC · re: Jon Smirl · lore

Re: git push failing, unpacker error

On 11/9/07, Jon Smirl <jonsmirl@gmail.com> wrote:

> I updated both sides to current git and it still fails. How do I debug this?
> What's causing this, "error: pack-objects died with strange error"?

My remote host is running 2.4.32, is git ok on that kernel?

Show 27 quoted lines

>
>
> jonsmirl@terra:~/mpc5200b$ git push dreamhost
> To ssh://jonsmirl1@git.digispeaker.com/~/mpc5200b.git
>  * [new branch]      m24 -> linus/m24
>  * [new branch]      m25 -> linus/m25
>  * [new branch]      m26 -> linus/m26
>  * [new branch]      m28 -> linus/m28
>  * [new branch]      m29 -> linus/m29
> Counting objects: 81156, done.
> Compressing objects: 100% (15280/15280), done.
> error: pack-objects died with strange errorMiB | 412 KiB/s
> unpack index-pack abnormal exit
> ng refs/remotes/linus/m24 n/a (unpacker error)
> ng refs/remotes/linus/m25 n/a (unpacker error)
> ng refs/remotes/linus/m26 n/a (unpacker error)
> ng refs/remotes/linus/m28 n/a (unpacker error)
> ng refs/remotes/linus/m29 n/a (unpacker error)
> error: failed to push to 'ssh://jonsmirl1@git.digispeaker.com/~/mpc5200b.git'
> jonsmirl@terra:~/mpc5200b$
>
>
>
> --
> Jon Smirl
> jonsmirl@gmail.com
>

-- 
Jon Smirl
jonsmirl@gmail.com

Junio C Hamano· Nov 9, 2007, 17:51 UTC · re: Jon Smirl · lore

Re: git push failing, unpacker error

"Jon Smirl" <jonsmirl@gmail.com> writes:

Show 5 quoted lines

> On 11/9/07, Jon Smirl <jonsmirl@gmail.com> wrote:
>> I updated both sides to current git and it still fails. How do I debug this?
>> What's causing this, "error: pack-objects died with strange error"?
>
> My remote host is running 2.4.32, is git ok on that kernel?

No problem that I am aware of. We are not *that* intimate with the kernel.

Do "git-fsck --full" on both repositories pass?

Jon Smirl· Nov 9, 2007, 18:09 UTC · re: Junio C Hamano · lore

Re: git push failing, unpacker error

On 11/9/07, Junio C Hamano <gitster@pobox.com> wrote:

Show 12 quoted lines

> "Jon Smirl" <jonsmirl@gmail.com> writes:
>
> > On 11/9/07, Jon Smirl <jonsmirl@gmail.com> wrote:
> >> I updated both sides to current git and it still fails. How do I debug this?
> >> What's causing this, "error: pack-objects died with strange error"?
> >
> > My remote host is running 2.4.32, is git ok on that kernel?
>
> No problem that I am aware of.  We are not *that* intimate with
> the kernel.
>
> Do "git-fsck --full" on both repositories pass?

I've just discovered that the hosting company has a mechanism for killing processes that it believes are consuming too much memory. When git does it's mmap's it looks like it is using over 512MB of memory which causes it to get zapped. At least I think this is what is happening.

-- 
Jon Smirl
jonsmirl@gmail.com

Nicolas Pitre· Nov 9, 2007, 19:27 UTC · re: Jon Smirl · lore

Re: git push failing, unpacker error

On Fri, 9 Nov 2007, Jon Smirl wrote:

Show 19 quoted lines

> On 11/9/07, Junio C Hamano <gitster@pobox.com> wrote:
> > "Jon Smirl" <jonsmirl@gmail.com> writes:
> >
> > > On 11/9/07, Jon Smirl <jonsmirl@gmail.com> wrote:
> > >> I updated both sides to current git and it still fails. How do I debug this?
> > >> What's causing this, "error: pack-objects died with strange error"?
> > >
> > > My remote host is running 2.4.32, is git ok on that kernel?
> >
> > No problem that I am aware of.  We are not *that* intimate with
> > the kernel.
> >
> > Do "git-fsck --full" on both repositories pass?
> 
> I've just discovered that the hosting company has a mechanism for
> killing processes that it believes are consuming too much memory. When
> git does it's mmap's it looks like it is using over 512MB of memory
> which causes it to get zapped. At least I think this is what is
> happening.

You might be interested by the following config variables:

	core.packedGitWindowSize
	core.packedGitLimit
	core.deltaBaseCacheLimit
	pack.windowMemory
	pack.deltaCacheSize

Certainly one or more of them could be tweaked in the remote repo to solve your problem. But since your problem happens on push then you should look at the core variables first.

Nicolas