All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Adamson <jwa@urbancode.com>
To: git@vger.kernel.org
Subject: Debugging Git push failure
Date: Wed, 9 Feb 2011 13:57:11 -0500	[thread overview]
Message-ID: <AANLkTimcGtDKZ2YU0Z_pc-aRtp-etXFWZ9-drSzpS3KN@mail.gmail.com> (raw)

Several developers on my team are experiencing an occasional failure
during push.  A subsequent push executed immediately afterward the
failure will work fine.  We are a small team of developers (about 10)
and only a couple users seem to experience this and then only
intermittently (every few days).
This is happening on a LAN environment with otherwise reliable
connectivity.  We have some hook scripts for post-update and update
configured within the repo.

the server has git version 1.7.3.3 installed
$ cat /etc/issue
CentOS release 5.5 (Final)
Kernel \r on an \m
$ uname -a
Linux core1.example.com 2.6.18-194.26.1.el5 #1 SMP Tue Nov 9 12:54:20
EST 2010 x86_64 x86_64 x86_64 GNU/Linux

Here is some output from one of the users during two sequential runs
of `git push -v`.  This user is git version 1.7.3.1.msysgit.0 (though
similar behavior has been seen by another user with version 1.7.0.4 on
ubuntu 10.04 LTS)
>git push -v
Pushing to ssh://git.example.com/data/git/example/scratch/bdd/cssearch-mockup.git
Counting objects: 9, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 505 bytes, done.
Total 5 (delta 4), reused 0 (delta 0)
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
>git push -v
Pushing to ssh://git.example.com/data/git/example/scratch/bdd/cssearch-mockup.git
Counting objects: 9, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 505 bytes, done.
Total 5 (delta 4), reused 0 (delta 0)
To ssh://git.example.com/data/git/example/scratch/bdd/cssearch-mockup.git
  bffa1a7..8fd772d  master -> master


Anyone know what could be causing this and, just as important, how to
debug it and issues like it in the future?
Thanks for any help/insight which can be offered.
--Jeff

             reply	other threads:[~2011-02-09 18:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 18:57 Jeff Adamson [this message]
2011-02-10 19:06 ` Debugging Git push failure Neal Kreitzinger

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=AANLkTimcGtDKZ2YU0Z_pc-aRtp-etXFWZ9-drSzpS3KN@mail.gmail.com \
    --to=jwa@urbancode.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.