{"thread":{"id":"26457","subject":"Debugging Git push failure","startedAt":"2011-02-09T18:57:11Z","lastAt":"2011-02-10T19:06:09Z","messageCount":2,"participants":["Jeff Adamson","Neal Kreitzinger"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"160776","messageId":"AANLkTimcGtDKZ2YU0Z_pc-aRtp-etXFWZ9-drSzpS3KN@mail.gmail.com","threadId":"26457","inReplyTo":null,"subject":"Debugging Git push failure","fromName":"Jeff Adamson","fromEmail":"jwa@urbancode.com","sentAt":"2011-02-09T18:57:11Z","receivedAt":"2011-02-09T18:57:11Z","isPatch":false,"sender":{"key":"jwa@urbancode.com","avatar":null},"body":"Several developers on my team are experiencing an occasional failure\nduring push.  A subsequent push executed immediately afterward the\nfailure will work fine.  We are a small team of developers (about 10)\nand only a couple users seem to experience this and then only\nintermittently (every few days).\nThis is happening on a LAN environment with otherwise reliable\nconnectivity.  We have some hook scripts for post-update and update\nconfigured within the repo.\n\nthe server has git version 1.7.3.3 installed\n$ cat /etc/issue\nCentOS release 5.5 (Final)\nKernel \\r on an \\m\n$ uname -a\nLinux core1.example.com 2.6.18-194.26.1.el5 #1 SMP Tue Nov 9 12:54:20\nEST 2010 x86_64 x86_64 x86_64 GNU/Linux\n\nHere is some output from one of the users during two sequential runs\nof `git push -v`.  This user is git version 1.7.3.1.msysgit.0 (though\nsimilar behavior has been seen by another user with version 1.7.0.4 on\nubuntu 10.04 LTS)\n>git push -v\nPushing to ssh://git.example.com/data/git/example/scratch/bdd/cssearch-mockup.git\nCounting objects: 9, done.\nDelta compression using up to 8 threads.\nCompressing objects: 100% (5/5), done.\nWriting objects: 100% (5/5), 505 bytes, done.\nTotal 5 (delta 4), reused 0 (delta 0)\nfatal: The remote end hung up unexpectedly\nfatal: The remote end hung up unexpectedly\n>git push -v\nPushing to ssh://git.example.com/data/git/example/scratch/bdd/cssearch-mockup.git\nCounting objects: 9, done.\nDelta compression using up to 8 threads.\nCompressing objects: 100% (5/5), done.\nWriting objects: 100% (5/5), 505 bytes, done.\nTotal 5 (delta 4), reused 0 (delta 0)\nTo ssh://git.example.com/data/git/example/scratch/bdd/cssearch-mockup.git\n  bffa1a7..8fd772d  master -> master\n\n\nAnyone know what could be causing this and, just as important, how to\ndebug it and issues like it in the future?\nThanks for any help/insight which can be offered.\n--Jeff\n"},{"id":"160832","messageId":"4D543721.5050103@gmail.com","threadId":"26457","inReplyTo":"AANLkTimcGtDKZ2YU0Z_pc-aRtp-etXFWZ9-drSzpS3KN@mail.gmail.com","subject":"Re: Debugging Git push failure","fromName":"Neal Kreitzinger","fromEmail":"nkreitzinger@gmail.com","sentAt":"2011-02-10T19:06:09Z","receivedAt":"2011-02-10T19:06:09Z","isPatch":false,"sender":{"key":"nkreitzinger@gmail.com","avatar":null},"body":"On 2/9/2011 12:57 PM, Jeff Adamson wrote:\n> Several developers on my team are experiencing an occasional failure\n> during push.  A subsequent push executed immediately afterward the\n> failure will work fine.  We are a small team of developers (about 10)\n> and only a couple users seem to experience this and then only\n> intermittently (every few days).\n> This is happening on a LAN environment with otherwise reliable\n> connectivity.  We have some hook scripts for post-update and update\n> configured within the repo.\n>\n> the server has git version 1.7.3.3 installed\n> $ cat /etc/issue\n> CentOS release 5.5 (Final)\n> Kernel \\r on an \\m\n> $ uname -a\n> Linux core1.example.com 2.6.18-194.26.1.el5 #1 SMP Tue Nov 9 12:54:20\n> EST 2010 x86_64 x86_64 x86_64 GNU/Linux\n>\n> Here is some output from one of the users during two sequential runs\n> of `git push -v`.  This user is git version 1.7.3.1.msysgit.0 (though\n> similar behavior has been seen by another user with version 1.7.0.4 on\n> ubuntu 10.04 LTS)\n>> git push -v\n> Pushing to ssh://git.example.com/data/git/example/scratch/bdd/cssearch-mockup.git\n> Counting objects: 9, done.\n> Delta compression using up to 8 threads.\n> Compressing objects: 100% (5/5), done.\n> Writing objects: 100% (5/5), 505 bytes, done.\n> Total 5 (delta 4), reused 0 (delta 0)\n> fatal: The remote end hung up unexpectedly\n> fatal: The remote end hung up unexpectedly\n>> git push -v\n> Pushing to ssh://git.example.com/data/git/example/scratch/bdd/cssearch-mockup.git\n> Counting objects: 9, done.\n> Delta compression using up to 8 threads.\n> Compressing objects: 100% (5/5), done.\n> Writing objects: 100% (5/5), 505 bytes, done.\n> Total 5 (delta 4), reused 0 (delta 0)\n> To ssh://git.example.com/data/git/example/scratch/bdd/cssearch-mockup.git\n>    bffa1a7..8fd772d  master ->  master\n>\n>\n> Anyone know what could be causing this and, just as important, how to\n> debug it and issues like it in the future?\n> Thanks for any help/insight which can be offered.\n> --Jeff\nI don't use ssh, but I use the git:// protocol and have also had push \nerrors locally.  I run RHEL and when I get errors with git protocol I \ncheck /var/log/messages.  Find out where your log messages are going and \ncheck them.  You could also check permissions on the destination repo. \nLook at its object store recursively, ie. .git/objects/, and do \"ls -la\" \nto see the permissions.  People could be pushing stuff up with the wrong \npermissions and then someone else can't get to it.  Just some ideas...\n\nv/r,\nNeal\n"}]}