963469 - git.mozilla.org taking too long to pack gecko; closes connection

Status: RESOLVED FIXED

(Developer Services :: General, task)

Description

[Andreas Pehrson [:pehrsons]]

To reproduce: git clone http://git.mozilla.org/releases/gecko.git &> log

The contents of log after this command:
  Cloning into 'gecko'...
  error: RPC failed; result=18, HTTP code = 200
  fatal: The remote end hung up unexpectedly
  fatal: protocol error: bad pack header

The piping to a log causes git to run in a non-interactive shell, in turn calling this:
git fetch-pack --stateless-rpc --stdin --lock-pack --thin --no-progress http://git.mozilla.org/releases/gecko.git/

The --no-progress flag causes it to fail. See more here: http://git.661346.n2.nabble.com/Cannot-clone-redirecting-stdout-td3621855.html

The timeout on git.mozilla.org seems to be 1 minute:
$> time git clone http://git.mozilla.org/releases/gecko.git &> log

real	1m1.943s
user	0m0.004s
sys	0m0.004s

Comment 1

[Kendall Libby [:fubar] (he/him)]

Aaaaah, thank you for finding that nabble link; this has been around for a bit (see bugs 857158 and 915221). Sadly, the associated patch (http://git.kaarsemaker.net/git/commit/7b8315bb593c38ac957486916512e9a5df6df087/) is rather more recent than out version of git (1.7.11.3).  (None of the timeouts that we have set are at 1 minute)

Comment 2

[Kendall Libby [:fubar] (he/him)]

Aaaarrrrrrgggggghhhhhh.  After a conversation in #infra with :catlee and :dustin about bug 857158, I discovered that the Timeout in httpd.conf was set to 60 seconds. Bumped it up to 300 to match Zeus, and it completed successfully. 

Please verify and let me know that it works for you.

Comment 3

[Andreas Pehrson [:pehrsons]]

Works great here now! Thanks for the quick turnaround Kendall :)

May I ask what is holding you from upgrading git?

Comment 4

[Kendall Libby [:fubar] (he/him)]

Mostly it's finding time to get it in place in staging and then have RelEng (and potentially partners) test to make sure it works as expected.