assistance with git error

assistance with git error

[Tom]

Could someone provide me some assistance with troubleshooting the following:

remote: Counting objects: 31654, done.
error: pack-objects died of signal 99568/19585)   
error: git upload-pack: git-pack-objects died with error.
fatal: git upload-pack: aborting due to possible repository
corruption on the remote side.
remote: aborting due to possible repository corruption on the remote side.
fatal: early EOF
fatal: index-pack failed


i know next to nothing about git and was asked to resolve this issue.

thank you.
tom

Re: assistance with git error

[Jeff King]

On Tue, Feb 24, 2015 at 08:40:56PM +0000, Tom wrote:

> Could someone provide me some assistance with troubleshooting the following:
> 
> remote: Counting objects: 31654, done.
> error: pack-objects died of signal 99568/19585)   

The output is smushed here due to the use of "\r" for the progress
reporting, but the interesting message is:

  error: pack-objects died of signal 9

which probably overwrote something like:

  remote: Compressing objects:  XXX% (9568/19585)

The rest of the messages are just the error propagating through the
various programs on the remote and local sides. So something killed
pack-objects with signal 9 (SIGKILL). Just a guess, but it may have been
killed for using too much memory.

Do you have control of the server? Is it running Linux? If so, check
your system logs to see if the OOM-killer killed it.

If the server is multi-core, setting:

  git config pack.threads 1

in the repository in question may reduce the peak memory usage.

-Peff

Re: assistance with git error

[Jeff King]

On Tue, Feb 24, 2015 at 04:49:00PM -0500, Thomas Moretto wrote:

> i also have a question concerning large files.

Sure, but let's take it back on-list. Then other people can help answer,
and later users can benefit from seeing the answers.

> i ran a check and it said there was a schema.sql file that was 1.2G(i followed this guide:  http://stevelorek.com/how-to-shrink-a-git-repository.html)

Running verify-pack like that is slow. If you have a recent version of
git, you can use:

  git rev-list --objects --all |
  git cat-file --batch-check='%(objectsize:disk) %(objectname) %(rest)' |
  sort -rn

to get a sorted list of the largest objects that are reachable. If you
don't see your big object there, try doing:

  git rev-list --objects --reflog

for the first line, to see if it shows up in the reflog.

If the object is only in the reflog, the simplest thing is to expire the
reflog and repack:

  git reflog expire --expire-unreachable=now --all
  git gc --prune=now

If it is reachable, then you'll have to actually rewrite history to get
rid of it. Since you know the sha1 of the object, you can find which
commit introduced it with:

  sha1=...whatever...
  git log --all --no-abbrev --raw | less +/$sha1

That will dump you in less, with the sha1 highlighted (if it comes and
goes through history, you may need to use "/" to find other instances).

-Peff