threads / discuss / 24130

unpacker error on push

Subject: unpacker error on push

## tl;dr

10 messages between Jun 16, 2010 and Jun 22, 2010.

replies: 9people: 2as markdown or json

Gavin Kistner· Jun 16, 2010, 15:46 UTC · lore
(my apologies if you receive this twice; I sent it once before I was authenticated on the mailing list)
Local: OS X 10.6.3, git 1.7.1
Remote: Ubuntu Lucid, git 1.7.0.4
How can I fix whatever is broken so that I can push again, and—more importantly—get the important changes I made last night over to the remote, by hook or by crook?

-_-_-_-_-_-_-_-_-_-_ On the local machine -_-_-_-_-_-_-_-_-_-_

Slim2:bugbot3 phrogz$ git push Counting objects: 70, done. Delta compression using up to 2 threads. Compressing objects: 100% (31/31), done. Writing objects: 100% (40/40), 26.91 KiB, done. Total 40 (delta 11), reused 37 (delta 8) error: unpack failed: unpack-objects abnormal exit To git://10.20.16.110/bugbot3.git ! [remote rejected] planning -> planning (n/a (unpacker error)) error: failed to push some refs to 'git://10.20.16.110/bugbot3.git'

Slim2:bugbot3 phrogz$ cat .git/config 
[core]
	repositoryformatversion = 0
	filemode = true
	bare = false
	logallrefupdates = true
	ignorecase = true
[remote "origin"]
	url = git://10.20.16.110/bugbot3.git
	fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
	remote = origin
	merge = refs/heads/master

Slim2:bugbot3 phrogz$ git status # On branch planning nothing to commit (working directory clean)

Slim2:bugbot3 phrogz$ git pull origin planning
From git://10.20.16.110/bugbot3
* branch            planning   -> FETCH_HEAD
Already up-to-date.

Slim2:bugbot3 phrogz$ git fsck --full (no output)

-_-_-_-_-_-_-_-_-_-_ On the remote -_-_-_-_-_-_-_-_-_-_ phrogz@gitbox:/pub/scm/bugbot3$ git config -l user.name=Gavin Kistner user.email=!@phrogz.net core.repositoryformatversion=0 core.filemode=false core.bare=false core.logallrefupdates=true core.ignorecase=true

phrogz@gitbox:/pub/scm/bugbot3$ git fsck --full (no output)

----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------

Nicolas Pitre· Jun 16, 2010, 19:34 UTC · re: Gavin Kistner · lore

Re: unpacker error on push

On Wed, 16 Jun 2010, Gavin Kistner wrote:
> (my apologies if you receive this twice; I sent it once before I was 
> authenticated on the mailing list)
This list doesn't require you to be subscribed for you to post messages.
Show 18 quoted lines
> Local: OS X 10.6.3, git 1.7.1
> Remote: Ubuntu Lucid, git 1.7.0.4
> 
> How can I fix whatever is broken so that I can push again, and—more 
> importantly—get the important changes I made last night over to the 
> remote, by hook or by crook?> -_-_-_-_-_-_-_-_-_-_ On the local 
> machine -_-_-_-_-_-_-_-_-_-_
> 
> Slim2:bugbot3 phrogz$ git push
> Counting objects: 70, done.
> Delta compression using up to 2 threads.
> Compressing objects: 100% (31/31), done.
> Writing objects: 100% (40/40), 26.91 KiB, done.
> Total 40 (delta 11), reused 37 (delta 8)
> error: unpack failed: unpack-objects abnormal exit
> To git://10.20.16.110/bugbot3.git
> ! [remote rejected] planning -> planning (n/a (unpacker error))
> error: failed to push some refs to 'git://10.20.16.110/bugbot3.git'

Could you try doing "git config receive.unpackLimit 1" on the _remote_ machine in the receiving repository?

Note this is not a proper fix but rather an attempt to isolate the issue. Please make a backup of the entire repository both on the local and the remote machine if you can, so the failure can be reproduced again after restoring them to the current state in case this would "fix" the issue.

Nicolas
Gavin Kistner· Jun 17, 2010, 04:41 UTC · re: Nicolas Pitre · lore

Re: unpacker error on push

On Jun 16, 2010, at 1:34 PM, Nicolas Pitre wrote:
Show 20 quoted lines
> On Wed, 16 Jun 2010, Gavin Kistner wrote:
>> Slim2:bugbot3 phrogz$ git push
>> Counting objects: 70, done.
>> Delta compression using up to 2 threads.
>> Compressing objects: 100% (31/31), done.
>> Writing objects: 100% (40/40), 26.91 KiB, done.
>> Total 40 (delta 11), reused 37 (delta 8)
>> error: unpack failed: unpack-objects abnormal exit
>> To git://10.20.16.110/bugbot3.git
>> ! [remote rejected] planning -> planning (n/a (unpacker error))
>> error: failed to push some refs to 'git://10.20.16.110/bugbot3.git'
> 
> Could you try doing "git config receive.unpackLimit 1" on the _remote_ 
> machine in the receiving repository?
> 
> Note this is not a proper fix but rather an attempt to isolate the 
> issue.  Please make a backup of the entire repository both on the local 
> and the remote machine if you can, so the failure can be reproduced 
> again after restoring them to the current state in case this would "fix" 
> the issue.
Sorry, I'd love to help but I zipped up the repo (sans .git or a few other directories), nuked it, and re-cloned. That fixed the issue.

I'll definitely save copies of the repositories next time something funky happens. ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------

Gavin Kistner· Jun 18, 2010, 17:25 UTC · re: Nicolas Pitre · lore

Re: unpacker error on push

On Jun 16, 2010, at 1:34 PM, Nicolas Pitre wrote:
Show 22 quoted lines
> On Wed, 16 Jun 2010, Gavin Kistner wrote:
>> Local: OS X 10.6.3, git 1.7.1
>> Remote: Ubuntu Lucid, git 1.7.0.4
>> 
>> How can I fix whatever is broken so that I can push again, and—more 
>> importantly—get the important changes I made last night over to the 
>> remote, by hook or by crook?> -_-_-_-_-_-_-_-_-_-_ On the local 
>> machine -_-_-_-_-_-_-_-_-_-_
>> 
>> Slim2:bugbot3 phrogz$ git push
>> Counting objects: 70, done.
>> Delta compression using up to 2 threads.
>> Compressing objects: 100% (31/31), done.
>> Writing objects: 100% (40/40), 26.91 KiB, done.
>> Total 40 (delta 11), reused 37 (delta 8)
>> error: unpack failed: unpack-objects abnormal exit
>> To git://10.20.16.110/bugbot3.git
>> ! [remote rejected] planning -> planning (n/a (unpacker error))
>> error: failed to push some refs to 'git://10.20.16.110/bugbot3.git'
> 
> Could you try doing "git config receive.unpackLimit 1" on the _remote_ 
> machine in the receiving repository?
I ran into this problem again. I backed up both repositories in full, ran the command above in the remote repository, and it did not fix the problem.
I deleted my local copy and cloned using ssh instead if git://, copied over the same changes and was able to push again. This looks to be my workaround.

If anyone wants to dive deeper into this problem, please let me know and we can fight it using the snapshots I have. ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------

Nicolas Pitre· Jun 18, 2010, 17:35 UTC · re: Gavin Kistner · lore

Re: unpacker error on push

On Fri, 18 Jun 2010, Gavin Kistner wrote:
Show 27 quoted lines
> On Jun 16, 2010, at 1:34 PM, Nicolas Pitre wrote:
> > On Wed, 16 Jun 2010, Gavin Kistner wrote:
> >> Local: OS X 10.6.3, git 1.7.1
> >> Remote: Ubuntu Lucid, git 1.7.0.4
> >> 
> >> How can I fix whatever is broken so that I can push again, and—more 
> >> importantly—get the important changes I made last night over to the 
> >> remote, by hook or by crook?> -_-_-_-_-_-_-_-_-_-_ On the local 
> >> machine -_-_-_-_-_-_-_-_-_-_
> >> 
> >> Slim2:bugbot3 phrogz$ git push
> >> Counting objects: 70, done.
> >> Delta compression using up to 2 threads.
> >> Compressing objects: 100% (31/31), done.
> >> Writing objects: 100% (40/40), 26.91 KiB, done.
> >> Total 40 (delta 11), reused 37 (delta 8)
> >> error: unpack failed: unpack-objects abnormal exit
> >> To git://10.20.16.110/bugbot3.git
> >> ! [remote rejected] planning -> planning (n/a (unpacker error))
> >> error: failed to push some refs to 'git://10.20.16.110/bugbot3.git'
> > 
> > Could you try doing "git config receive.unpackLimit 1" on the _remote_ 
> > machine in the receiving repository?
> 
> I ran into this problem again. I backed up both repositories in full, 
> ran the command above in the remote repository, and it did not fix the 
> problem.
The error message changed a bit though, right?
Show 6 quoted lines
> I deleted my local copy and cloned using ssh instead if git://, copied 
> over the same changes and was able to push again. This looks to be my 
> workaround.
> 
> If anyone wants to dive deeper into this problem, please let me know 
> and we can fight it using the snapshots I have. 
I would be interested in them.
Nicolas
Gavin Kistner· Jun 18, 2010, 17:41 UTC · re: Nicolas Pitre · lore

Re: unpacker error on push

On Jun 18, 2010, at 11:35 AM, Nicolas Pitre wrote:
Show 31 quoted lines
> On Fri, 18 Jun 2010, Gavin Kistner wrote:
> 
>> On Jun 16, 2010, at 1:34 PM, Nicolas Pitre wrote:
>>> On Wed, 16 Jun 2010, Gavin Kistner wrote:
>>>> Local: OS X 10.6.3, git 1.7.1
>>>> Remote: Ubuntu Lucid, git 1.7.0.4
>>>> 
>>>> How can I fix whatever is broken so that I can push again, and—more 
>>>> importantly—get the important changes I made last night over to the 
>>>> remote, by hook or by crook?> -_-_-_-_-_-_-_-_-_-_ On the local 
>>>> machine -_-_-_-_-_-_-_-_-_-_
>>>> 
>>>> Slim2:bugbot3 phrogz$ git push
>>>> Counting objects: 70, done.
>>>> Delta compression using up to 2 threads.
>>>> Compressing objects: 100% (31/31), done.
>>>> Writing objects: 100% (40/40), 26.91 KiB, done.
>>>> Total 40 (delta 11), reused 37 (delta 8)
>>>> error: unpack failed: unpack-objects abnormal exit
>>>> To git://10.20.16.110/bugbot3.git
>>>> ! [remote rejected] planning -> planning (n/a (unpacker error))
>>>> error: failed to push some refs to 'git://10.20.16.110/bugbot3.git'
>>> 
>>> Could you try doing "git config receive.unpackLimit 1" on the _remote_ 
>>> machine in the receiving repository?
>> 
>> I ran into this problem again. I backed up both repositories in full, 
>> ran the command above in the remote repository, and it did not fix the 
>> problem.
> 
> The error message changed a bit though, right?
Yes, it failed in "index-pack" instead of "unpack-objects". Here's the new result:
Counting objects: 116, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (63/63), done.
Writing objects: 100% (63/63), 11.19 KiB, done.
Total 63 (delta 40), reused 0 (delta 0)
error: unpack failed: index-pack abnormal exit
To git://10.20.16.110/bugbot3.git
 ! [remote rejected] planning -> planning (n/a (unpacker error))
error: failed to push some refs to 'git://10.20.16.110/bugbot3.git'
Show 8 quoted lines
>> I deleted my local copy and cloned using ssh instead if git://, copied 
>> over the same changes and was able to push again. This looks to be my 
>> workaround.
>> 
>> If anyone wants to dive deeper into this problem, please let me know 
>> and we can fight it using the snapshots I have. 
> 
> I would be interested in them.

OK, I'll coordinate with you off-list. ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------

Nicolas Pitre· Jun 18, 2010, 17:54 UTC · re: Gavin Kistner · lore

Re: unpacker error on push

On Fri, 18 Jun 2010, Gavin Kistner wrote:
Show 8 quoted lines
> On Jun 18, 2010, at 11:35 AM, Nicolas Pitre wrote:
> > On Fri, 18 Jun 2010, Gavin Kistner wrote:
> >> If anyone wants to dive deeper into this problem, please let me know 
> >> and we can fight it using the snapshots I have. 
> > 
> > I would be interested in them.
> 
> OK, I'll coordinate with you off-list.

I got them now. Weekend is coming soon so I might not have time to look at it right away though.

Nicolas
Gavin Kistner· Jun 18, 2010, 17:55 UTC · re: Nicolas Pitre · lore

RE: unpacker error on push

No problem; like I said, the ssh-based solution seems to be working for now, so I'm unblocked in my workflow. Diving deeper on this issue is largely interesting to improve git.
-----Original Message-----
From: Nicolas Pitre [mailto:nico@fluxnic.net] 
Sent: Friday, June 18, 2010 11:55 AM
To: Gavin Kistner
Cc: git@vger.kernel.org
Subject: Re: unpacker error on push
On Fri, 18 Jun 2010, Gavin Kistner wrote:
Show 8 quoted lines
> On Jun 18, 2010, at 11:35 AM, Nicolas Pitre wrote:
> > On Fri, 18 Jun 2010, Gavin Kistner wrote:
> >> If anyone wants to dive deeper into this problem, please let me know 
> >> and we can fight it using the snapshots I have. 
> > 
> > I would be interested in them.
> 
> OK, I'll coordinate with you off-list.

I got them now. Weekend is coming soon so I might not have time to look at it right away though.

Nicolas ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------

Nicolas Pitre· Jun 22, 2010, 00:58 UTC · re: Gavin Kistner · lore

Re: unpacker error on push

On Fri, 18 Jun 2010, Gavin Kistner wrote:
Show 12 quoted lines
> On Jun 18, 2010, at 11:35 AM, Nicolas Pitre wrote:
> > On Fri, 18 Jun 2010, Gavin Kistner wrote:
> >> I deleted my local copy and cloned using ssh instead if git://, copied 
> >> over the same changes and was able to push again. This looks to be my 
> >> workaround.
> >> 
> >> If anyone wants to dive deeper into this problem, please let me know 
> >> and we can fight it using the snapshots I have. 
> > 
> > I would be interested in them.
> 
> OK, I'll coordinate with you off-list.

Well... I just can't reproduce the issue with those repositories you provided me with. Neither over git:// nor file:// nor ssh://. But all I have here are Linux machines, no OSX.

Could you try pushing from a Linux machine by chance? Maybe this is an OSX related issue.

Nicolas
Gavin Kistner· Jun 22, 2010, 14:04 UTC · re: Nicolas Pitre · lore

Re: unpacker error on push

On Jun 21, 2010, at 6:58 PM, Nicolas Pitre wrote:
Show 6 quoted lines
> Well... I just can't reproduce the issue with those repositories you 
> provided me with.  Neither over git:// nor file:// nor ssh://.  But all 
> I have here are Linux machines, no OSX.
> 
> Could you try pushing from a Linux machine by chance?  Maybe this is an 
> OSX related issue.
I don't have a second linux box to test with, unfortunately.

I will say that I experienced the same problem with a Windows box trying to push to the same repository over git://, and had to switch it to ssh also. ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------

← back to recent threads