Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • 1
    Have tried any of the suggestions in the SO Q&A? Also what does strace -p <pid of hung git daemon> say it's blocking on? Commented Jul 7, 2014 at 22:44
  • @slm Do you have any specific suggestions in mind? Commented Jul 8, 2014 at 10:13
  • 1
    What fixed for me was making sure Jenkins was running as the user with proper credentials to the GIT repos Commented Jul 23, 2015 at 20:46
  • 1
    That's what git-upload-pack is supposed to do, AFAICT. It's waiting for you to speak the git fetch-pack protocol and tell it which things to send (try running it on a local repository, you'll get the same output). Commented Jun 3, 2016 at 17:34
  • 2
    (Presuming this question isn't obsolete, as it's from 2013) Does a fresh git clone (from github) work on the host that Jenkins is trying to fetch on? I suspect it won't, and you probably have a Path MTU discovery issue caused by a broken firewall (which might be anywhere on the path—not just your side.) Commented Jun 3, 2016 at 17:36