1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues


Issue #7467 resolved

error: pack-objects died with strange error

Amanda Kuek
created an issue

Hi there,

Firstly, Bitbucket is amazing, so thanks very much.

I have been using it without issue for a while, but recently (since yesterday morning) I have reliably come up against this error whenever I try to push.

Counting objects: 639, done. Delta compression using up to 2 threads. Compressing objects: 100% (628/628), done. Read from remote host bitbucket.org: Connection reset by peer fatal: sha1 file '<stdout>' write error: Invalid argument error: pack-objects died with strange error error: failed to push some refs to 'git@bitbucket.org:xxxxxxxxx/yyy.git'

(I have blanked out the repository name)

I can do 3 pushes in a row that end in this error, then the 4th will push successfully (as an example of how it sometimes works and sometimes doesn't).

I am not really sure what is causing it, and would appreciate any help you can provide.

Thank you, Amanda.

Comments (7)

  1. Brian Nguyen

    Hi Amanda,

    How large are the files/commits you are pushing up to bitbucket.org? Large files like images or pdfs can take a while and may cause the connection to close.

    Alternatively, there may be an issue with your local git repository so you can you try running:

    git fsck

    This may help.

    Cheers, Brian

  2. Amanda Kuek reporter

    Hi Brian,

    Thanks for your reply. Each push was between 20MB to 45MB. What seemed strange about it was that "Writing objects" would often get up to 100% (a process that would usually take about 5 to 10 minutes), but still end in an error. Is it too large?

    I am trying 'git fsck' now, thanks for that.

    Cheers, Amanda.

  3. Brian Nguyen

    Hi Amanda,

    That's not all that much. From your description, I suspect that our post-receive hooks are taking a while to fire. Would you be able to tell us what repository(ies) is causing you issues? That way we can look to see if there is anything untoward in the repository.

    If you are not comfortable giving us this information here, you can send us an email at support@bitbucket.org.

    Cheers, Brian

  4. Amanda Kuek reporter

    Hi Brian,

    Thanks for replying. Actually, after running 'git fsck' I haven't experienced any further errors. I think that might have fixed it, so thanks for that!

    Hope you have a good weekend.

    Cheers, Amanda.

  5. Log in to comment